Subject:
Re: Suggestions on getting Epson 1250 usb scanner working
From:
Gene Heskett ####@####.####
Date:
16 Feb 2002 15:00:37 -0000
Message-Id: <20020216145019473.AAA694@mail.iolinc.net@there>
On Saturday 16 February 2002 07:45 am, Stealth Dave wrote:
>On Sat, 2002-02-16 at 02:54, Gene Heskett wrote:
>> I too have one of these beasts. One must either setup an
>> alias in your modules.conf, or add it to the list in the
>> kernels scanner.h and recompile, which is what I've done over
>> the last 2-3 kernel upgrades. Unforch, I'm still running
>> 2.4.17 because its the last one that will both build, and work
>> with iptables.
>
>I'm pretty confident that I have the kernel module set up
> correctly. As I've said, sane-find-scanner finds the scanner
> with no problems. However, no sane front-end (i.e. scanimage or
> xsane) can find it.
Either requires that an insmod scanner be done before
running, so I asume an lsmod shows the scanner module.
Sane-find-scanner only finds a /dev/descriptor that
responds, scanimage -L needs to correlate the
vendor/product codes it gets in order to translate from
those to 'Epson Perfection 1250U'
Try adding those vendor/product numbers to your
linux/drivers/usb/scanner.h file and rebuild your kernel.
I stuck mine in the middle of the listing so they were
in order numericly. I doubt if it cares about the order though. :)
Of course I've been told I do things the hard way before.
[snip]
>I looked back through the archives (oh, for a search feature!),
> and the only article that I could come up with for reference
> was this:
>
>http://www.linuxhacker.org/cgi-bin/ezmlm-cgi?3:mss:814:200112
>
>It mentions changing the Cap and HW entries for the Epson 1250
> from _2 on the end to _5. Well, the end of the Cap and HW
> entries in the most recent patch are _0. Being fearless, I
> went ahead and changed them anyway, and it failed to compile,
> because the pointer names had changed (I think; my beginning C
> class in college was 9 years ago and I never went further with
> it).
As an old (67) fart with an 8th grade education, I've managed
to do C well enough to fix what I need fixed. I have about a
3 foot shelf full of C books, starting with both issues of the
K&R reference. Most are copycat stuff though :-(
> So I changed the pointer names as well, it compiled, and
> same result. I'm starting to think that I either misunderstood
> the instructions, or they no longer apply to the most recent
> builds. Could you take a look at it and shed some light on the
> subject for me?
This will take some cut & paste, but here they are:
-----------------------------------
/* Epson Perfection/Photo1250
* NS9832 + Button + CCD????
*/
static DCapsDef Cap0x04B8_0x010F_0 =
{
{{ 27, 80 }, 10, {2550, 3568}, { 100, 100 }, COLOR_BW },
{{ 0, 0}, 0, {0, 0}, { 0, 0 }, 0 },
{{ 0, 0}, 0, {0, 0}, { 0, 0 }, 0 },
{{ 0, 0}, 0, {0, 0}, { 0, 0 }, 0 },
{1200, 1200},
0,
SENSORORDER_rgb,
8, /* sensor distance */
4, /* number of buttons */
kNEC8861, /* use default settings during calibration */
0, /* not used here... */
_WAF_MISC_IO6_LAMP /* use miscio 6 for lamp switching */
};
---------------------------
and
---------------------------
/* EPSON Perfection/Photo 1250 */
static HWDef Hw0x04B8_0x010F_0 =
{
1.0, /* dMaxMotorSpeed (Max_Speed) */
0.9, /* dMaxMoveSpeed (Max_Speed) */
12, /* wIntegrationTimeLowLamp */
12, /* wIntegrationTimeHighLamp */
600, /* wMotorDpi (Full step DPI) */
512, /* wRAMSize (KB) */
4, /* wMinIntegrationTimeLowres (ms) */
5, /* wMinIntegrationTimeHighres (ms) */
3000, /* ok wGreenPWMDutyCycleLow (reg 0x2a + 0x2b) */
4095, /* ok wGreenPWMDutyCycleHigh (reg 0x2a + 0x2b) */
0x02, /* ok bSensorConfiguration (0x0b) */
0x04, /* ok sensor control settings (reg 0x0c) */
0x7f, /* ok sensor control settings (reg 0x0d) */
0x13, /* ok sensor control settings (reg 0x0e) */
{0x02, 0x07, 0x00, 0x01, 0x00, 0x00, 0x00, 0x00, 0x04, 0x00},
/* ?? mono (reg 0x0f to 0x18) */
{0x06, 0x16, 0x00, 0x05, 0x0c, 0x17, 0x00, 0x00, 0x08, 0x14},
/* ok color (reg 0x0f to 0x18) */
_GREEN_CH, /* ok bReg_0x26 color mode - bits 4 and 5 */
0x40, /* ok bReg 0x27 color mode */
1, /* ok StepperPhaseCorrection (reg 0x1a + 0x1b) */
0x00, /* ok bOpticBlackStart (reg 0x1c) */
0x42, /* ok bOpticBlackEnd (reg 0x1d) */
69, /* ok wActivePixelsStart (reg 0x1e + 0x1f) */
10766, /* ok wLineEnd (reg 0x20 + 0x21) */
16383, /* ok red lamp on (reg 0x2c + 0x2d) */
0, /* ok red lamp off (reg 0x2e + 0x2f) */
16383, /* ok green lamp on (reg 0x30 + 0x31) */
0, /* ok green lamp off (reg 0x32 + 0x33) */
16383, /* ok blue lamp on (reg 0x34 + 0x35) */
0, /* ok blue lamp off (reg 0x36 + 0x37) */
3, /* ok stepper motor control (reg 0x45) */
0, /* ok wStepsAfterPaperSensor2 (reg 0x4c + 0x4d) */
0x0c, /* ok acceleration profile (reg 0x51) */
0, /* ok lines to process (reg 0x54) */
0x0f, /* ok kickstart (reg 0x55) */
0x02, /* ok pwm freq (reg 0x56) */
1, /* ok pwm duty cycle (reg 0x57) */
0x0d, /* ok Paper sense (reg 0x58) */
0x41, /* ok misc io12 (reg 0x59) */
0x44, /* ok misc io34 (reg 0x5a) */
0x49, /* ok misc io56 (reg 0x5b) */
0, /* ok test mode ADC Output CODE MSB (reg 0x5c) */
0, /* ok test mode ADC Output CODE LSB (reg 0x5d) */
0, /* ok test mode (reg 0x5e) */
SANE_FALSE, /* has a lm9831? */
MODEL_NOPLUSTEK
};
Just overwrite the two sections in your plustek-devs.c
file with these two snips.
I had also added a sleep(60) call in plustek-usbio.c right after
it turns the lamp on, figuring it might help some shading
problems related to an imperfect paint job on the calibration
strip, but it did no good at all, just wasted that minute.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
98.5+% setiathome rank, not too shabby for a hillbilly
