[sane-devel] Epson 1250 scanner does not return back after scanning

2004-10-30 Thread Henning Meier-Geinitz 
Hi,

On Thu, Oct 28, 2004 at 11:16:09AM +0200, Martin Motovsky wrote:
> [plustek] drvclose()
> [plustek] TIME END 1: 31s
> [plustek] usbDev_stopScan()
> [plustek] usbDev_ScanEnd(), start=1, park=1
> [plustek] reader_process: finished reading data
> [plustek] (SIG) Child is down (signal=20)
> scanimage: received signal 2
> scanimage: trying to stop scanner
> [plustek] sane_cancel

Looks like SIGCHILD called the plustek signal handler. However, also
the scanimage signal handler was called. What is sig 2 and sig 20 on
FreeBSD?

scanimage calls sane_cancel() in its own signal handler.

Bye,
  Henning

[sane-devel] Epson 1250 scanner does not return back after scanning

2004-10-28 Thread Olaf Meeuwissen 
Martin Motovsky  writes:

> Dear sirs,
>
> we have a problem with our Epson 1250 scanner. It scans an image correctly,
> but after scanning, a lamp remains be switched on and a scanner's header
> remains at the "end of the image" position. I.e. it does not return back to
> the original home position. Can somebody help us?

The lamp has to be switched off by the software.  I don't know if the
plustek backend does that.

> We have 
> - FreeBSD system
> - sane-backends-1.0.14
> - only unmarked driver in the dll.conf if a plustek driver

You may want to try the epkowa backend that comes as part of "Image
Scan! for Linux" which is downloadable via:

  http://www.epkowa.co.jp/english/linux_e/dl_scan.html

Hope this helps,
-- 
Olaf MeeuwissenEPSON KOWA Corporation, PF1
FSF Associate Member #1962   sign up at http://member.fsf.org/
GnuPG key: 6BE37D90/AB6B 0D1F 99E7 1BF5 EB97  976A 16C7 F27D 6BE3 7D90
Penguin's lib!   -- I hack, therefore I am --   LPIC-2

[sane-devel] Epson 1250 scanner does not return back after scanning

2004-10-28 Thread Martin Motovsky 
Thank you for previous advices.

While testing scanimage in the debug mode, I mentioned, that sometimes 
it finished scanning correctly and sometime not. Below is a debug 
output, when lamp remained on and scanner's header did not return back 
to original position.

Martin

---
I used this script:
export SANE_DEBUG_PLUSTEK=20 ; scanimage -d plustek:/dev/uscanner0 
--format tiff -l10 -t10 -x100 -y100 --resolution 150dpi --mode Color > 
test.tiff 2>log.txt

---
Here is a debug output:

[sanei_debug] Setting debug level of plustek to 20.
[plustek] Plustek backend V0.47-11, part of sane-backends 1.0.14
[plustek] ># Plustek-SANE Backend configuration file<
[plustek] ># For use with LM9831/2/3 based USB scanners<
[plustek] >#<
[plustek] ><
[plustek] ># each device needs at least two lines:<
[plustek] ># - [usb] vendor-ID and product-ID<
[plustek] ># - device devicename<
[plustek] ># i.e. for Plustek (0x07B3) UT12/16/24 (0x0017)<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device /dev/usbscanner<
[plustek] ># or<
[plustek] ># device libusb:bbb:ddd<
[plustek] ># where bbb is the busnumber and ddd the device number<
[plustek] ># make sure that your user has access to 
/proc/bus/usb/bbb/ddd<
[plustek] >#<
[plustek] ># additionally you can specify some options<
[plustek] ># warmup, lOffOnEnd, lampOff<
[plustek] >#<
[plustek] ># For autodetection use<
[plustek] ># [usb]<
[plustek] ># device /dev/usbscanner<
[plustek] >#<
[plustek] ># or simply<
[plustek] ># [usb]<
[plustek] >#<
[plustek] ># or if you want a specific device but you have no idea 
about the<
[plustek] ># device node or you use libusb, simply set vendor- and 
product-ID<
[plustek] ># [usb] 0x07B3 0x0017<
[plustek] ># device auto<
[plustek] >#<
[plustek] ># NOTE: autodetection is safe, as it uses the info it got<
[plustek] >#   from the USB subsystem. If you're not using the<
[plustek] >#   autodetection, you MUST have attached that device<
[plustek] >#   at your USB-port, that you have specified...<
[plustek] >#<
[plustek] ><
[plustek] >[usb]<
[plustek] next device uses autodetection
[plustek] ... next device
[plustek] ><
[plustek] >#<
[plustek] ># options for the previous USB entry<
[plustek] >#<
[plustek] ># switch lamp off after xxx secs, 0 disables the feature<
[plustek] >option lampOff 309<
[plustek] Decoding option >lampOff<
[plustek] ><
[plustek] ># warmup period in seconds, 0 means no warmup<
[plustek] >option warmup 15<
[plustek] Decoding option >warmup<
[plustek] ><
[plustek] ># 0 means leave lamp-status untouched, not 0 means switch 
off<
[plustek] ># on sane_close<
[plustek] >option lOffOnEnd 1<
[plustek] Decoding option >lOffOnEnd<
[plustek] ><
[plustek] >#<
[plustek] ># options to tweak the image start-position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] >#<
[plustek] ># for the normal scan area<
[plustek] >#<
[plustek] >option posOffX 0<
[plustek] Decoding option >posOffX<
[plustek] >option posOffY 0<
[plustek] Decoding option >posOffY<
[plustek] ><
[plustek] ># for transparencies<
[plustek] >option tpaOffX 0<
[plustek] Decoding option >tpaOffX<
[plustek] >option tpaOffY 0<
[plustek] Decoding option >tpaOffY<
[plustek] ><
[plustek] ># for negatives<
[plustek] >option negOffX 0<
[plustek] Decoding option >negOffX<
[plustek] >option negOffY 0<
[plustek] Decoding option >negOffY<
[plustek] ><
[plustek] >#<
[plustek] ># for setting the calibration strip position<
[plustek] ># (WARNING: there's no internal range check!!!)<
[plustek] ># -1 means use built in<
[plustek] >#<
[plustek] >option posShadingY -1<
[plustek] Decoding option >posShadingY<
[plustek] >option tpaShadingY -1<
[plustek] Decoding option >tpaShadingY<
[plustek] >option negShadingY -1<
[plustek] Decoding option >negShadingY<
[plustek] ><
[plustek] >#<
[plustek] ># to invert the negatives, 0 disables the feature<
[plustek] >#<
[plustek] >option invertNegatives 0<
[plustek] Decoding option >invertNegatives<
[plustek] ><
[plustek] >#<
[plustek] ># to save/restore coarse calibration data<
[plustek] >#<
[plustek] >option cacheCalData 0<
[plustek] Decoding option >cacheCalData<
[plustek] ><
[plustek] >#<
[plustek] ># use alternate calibration routines<
[plustek] >#<
[plustek] >option altCalibration 0<
[plustek] Decoding option >altCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping whole calibration step<
[plustek] >#<
[plustek] >option skipCalibration 0<
[plustek] Decoding option >skipCalibration<
[plustek] ><
[plustek] >#<
[plustek] ># for skipping entire fine calibration step<
[plustek] ># coarse calibration is done<
[plustek] >#<
[plustek] >option skipFine 0<
[plustek] Decoding option >skipFine<
[plustek] ><
[plustek] >#<
[plustek] ># discard the result of the fine white calibration<
[plustek] >#<
[plustek] >option skipFineWhite 0<
[plustek] Decoding option >skipFineWhite<
[plustek] ><
[plustek] ># for replacing the gain values found

[sane-devel] Epson 1250 scanner does not return back after scanning

2004-10-28 Thread Gerhard Jaeger 
On Mittwoch 27 Oktober 2004 22:20, Martin Motovsky wrote:
> Dear sirs,
>
> we have a problem with our Epson 1250 scanner. It scans an image correctly,
> but after scanning, a lamp remains be switched on and a scanner's header
> remains at the "end of the image" position. I.e. it does not return back to
> the original home position. Can somebody help us?
>
> We have
> - FreeBSD system
> - sane-backends-1.0.14
> - only unmarked driver in the dll.conf if a plustek driver
>
The lamp is switched off by the software and the behaviour can be setup
in the configuration file. Why the sensor gets stucked, I don't know.
Can you please retry and enabling the debug message before, i.e.
export SANE_DEBUG_PLUSTEK=20 ; scanimage [what-ever-parameter-you-need]

--
 Gerhard

[sane-devel] Epson 1250 scanner does not return back after scanning

2004-10-27 Thread Martin Motovsky 
Dear sirs,

we have a problem with our Epson 1250 scanner. It scans an image correctly,
but after scanning, a lamp remains be switched on and a scanner's header
remains at the "end of the image" position. I.e. it does not return back to
the original home position. Can somebody help us?

We have 
- FreeBSD system
- sane-backends-1.0.14
- only unmarked driver in the dll.conf if a plustek driver

Martin Motovsky