plustek: Thread: Epson 1250

Hi there,

after writing Gerhard and Gene direcly this morning, I just found that
there is also a mailing list (must have been sitting on my eyes).

I also got caught by the lamp problem, but I can confirm that the lamp
is not broken, as I tested it with win2k drivers this morning.

cu
	Reinhard

Hi Reinhard,

Thans for this info...
I've currently sent the LM9831 docs to Gene, so he will might be
able to find out more. As well I've sent him the hint, that in file
plustek.-devs.c, the HWDef  structure used for the Epson
contains a flag, that tells the driver, that a LM9832 is used
this flag should be set to SANE_TRUE, so the driver is informed,
that a LM9831 is inside the scanner...

Hope this helps...
   Gerhard

On Wednesday, 19. December 2001 19:28, Reinhard Max wrote:
> Hi there,
>
> after writing Gerhard and Gene direcly this morning, I just found that
> there is also a mailing list (must have been sitting on my eyes).
>
> I also got caught by the lamp problem, but I can confirm that the lamp
> is not broken, as I tested it with win2k drivers this morning.
>
> cu
> 	Reinhard
>

On Wednesday 19 December 2001 03:22 pm, Jaeger, Gerhard wrote:
>Hi Reinhard,
>
>Thans for this info...
>I've currently sent the LM9831 docs to Gene, so he will might be
>able to find out more. As well I've sent him the hint, that in
> file plustek.-devs.c, the HWDef  structure used for the Epson
> contains a flag, that tells the driver, that a LM9832 is used
> this flag should be set to SANE_TRUE, so the driver is
> informed, that a LM9831 is inside the scanner...

On arrival home, I immediatly changed that flag to SANE_TRUE and 
rebuilt it.  The green/red blinking pattern of the left button 
changed, becoming a bit more 'spastic', but the lamp is still 
dark 100% of the time, so while that may be required, its not the 
magic bullet that controls the lamp.

-- 
Cheers, Gene

Hi,

On Wed, 19 Dec 2001 at 21:22, Jaeger, Gerhard wrote:

> I've currently sent the LM9831 docs to Gene, so he will might be
> able to find out more.

I got some docs from http://www.connect.to/merlin .
Is there anything else?

> As well I've sent him the hint, that in file plustek.-devs.c, the
> HWDef structure used for the Epson contains a flag, that tells the
> driver, that a LM9832 is used this flag should be set to
> SANE_TRUE, so the driver is informed, that a LM9831 is inside the
> scanner...

I can confirm Gene's observation about the red/green light on the left
button. On my first try with SANE_TRUE the stepper motor came out of
sync and blocked, but later I couldn't reproduce this.

BTW, even when I set SANE_TRUE and run scanimage in debug mode, I get
a line saying:

	[plustek] usbio_DetectLM983x: found [plustek] LM9832

So my conclusion would be that the scanner really contains a LM9832,
or am I missing something?

cu
	Reinhard

Hi guys,

happy new year!

Any news about the EPSON1250? 

Gerhard

see link:
http://sane.informatik.uni-freiburg.de/cgi-bin/driver.pl?manu=epson+&model=1250&bus=usb

-------------------------------------------------------------------------------------------
***Protect your PC from local E-Mail Application security holes***
***Maintain your Privacy - Passport Free***

http://www.x-mail.net Web Based E-Mail

Voice Messages, Voice Calls, Live Chat, X-Mail Messenger,
Personal Web Hosting, 128 bit SSL Secure, Calendar, Bookmarks,
Forwarding

X-Mail Premium: 20MB Messages, 100MB Storage, POP3, Ad Free

I currently can scan as long as the scanner is the only usb device 
plugged in.  If I plug another usb device in, once the scanner warms up, 
moves a bit then just stops.  I happens with any device plugged into any 
port (printer, zip drive, camera).  Any ideas.  I'm using the 0.44_10 
with Redhat 8.0.  

Also I ran into a seg fault as soon as preview would complete. It 
happened everytime I tried to scan.  Heres the info and my quick fix (it 
might be the cause of my problem).  

GDB info:
Program received signal SIGSEGV, Segmentation fault.
0x4073b881 in usb_LampTimerIrq (sig=14) at plustek-usbhw.c:1093
1093            if( -1 == dev_xxx->fd ) {

I just added this to the at the beginning of usb_LampTimerIrq (not sure 
if its the right thing to do but it worked):

    if(dev_xxx == NULL)
        return;

Thanks in advance.

Hi Josh,

On Samstag, 1. Februar 2003 06:45, Josh Homan wrote:
> I currently can scan as long as the scanner is the only usb device
> plugged in.  If I plug another usb device in, once the scanner warms up,
> moves a bit then just stops.  I happens with any device plugged into any
> port (printer, zip drive, camera).  Any ideas.  I'm using the 0.44_10
> with Redhat 8.0.

interessting! Never saw this behaviour here! I Often use two or three
scanners on different usb-ports and additional my USB mouse. Might
be a problem of your kernel or usb subsystem...

> Also I ran into a seg fault as soon as preview would complete. It
> happened everytime I tried to scan.  Heres the info and my quick fix (it
> might be the cause of my problem).
>
> GDB info:
> Program received signal SIGSEGV, Segmentation fault.
> 0x4073b881 in usb_LampTimerIrq (sig=14) at plustek-usbhw.c:1093
> 1093            if( -1 == dev_xxx->fd ) {
>
> I just added this to the at the beginning of usb_LampTimerIrq (not sure
> if its the right thing to do but it worked):
>
>     if(dev_xxx == NULL)
>         return;

Good work, Gene Heskett reported that bug, which never shows up here.
You're right on that, I should check this pointer before using it...
At least this construction works only if I use the backend with one scanner -
but that's another story.

>
> Thanks in advance.

Thank you!
  Gerhard

Hi Gerhard,

    Thanks for the reply and thanks for the great work on the drivers. 
 I recompiled my kernel, setting my usb drivers to be modules and it 
appears to fix the problem (I was just lazy and didn't want to fight 
with loading them).  I have everything plugged in and the scanner is 
working great.  

Josh