Digital BW, The Print

On 7/27/2013 3:33 PM, livingwithbugs@... wrote:
>
> The paper I'm trying to use is 315 gsm (Innova STNW). Since the 
> printer is new (refurbished) I think the rollers are probably clean. 
> The problem is that the rollers grab the paper ok but then an error is 
> generated (flashing red light) and the paper is ejected. My guess is 
> there's a "paper thickness sensor" that is being triggered by the 
> slightly too thick paper. If I could set the "envelope" switch the 
> print head would move a little further away from the paper. 
> Unfortunately the envelope setting is done in the driver instead of 
> manually (I think).
>
> Thanks
>
> Jack DeAngelis
>
> --- In DigitalBlackandWhiteThePrint@yahoogroups.com 
> <mailto:DigitalBlackandWhiteThePrint%40yahoogroups.com>, Paul Roark 
> <roark.paul@...> wrote:
> >
> > 300 gsm papers go through a 1400 with just a little manual assist in
> > feeding; no driver or other changes are needed.
> >
> > If they don't it's usually because the feed roller is dirty. Some papers
> > foul it. Running a sheet through that is sprayed with Windex seems 
> to work
> > to clean the roller(s).
> >
> > Paul
> > www.PaulRoark.com
> >
> >
> > On Sat, Jul 27, 2013 at 11:57 AM, <livingwithbugs@...> wrote:
> >
> > > **
> > >
> > >
> > > I am setting up a refurbished Epson 1400 and running into the 
> (well know?)
> > > issues with thick papers. As I understand it the paper thickness 
> is set in
> > > the driver not buy a lever as in older printers. The problem is I am
> > > running under linux so I don't use Win or Mac drivers. Has anyone else
> > > encountered this dilemma?
> > >
> > >
> > >
> >
> >
> > [Non-text portions of this message have been removed]
>
*Try running an Epson adhesive page through your printer. Paper dust on 
rollers can cause the problem you describe. I usually run my own 
adhesive pages (several vertical mounted strips of double sided 1/2 - 
3/4" scotch tape on a page of typing paper) through my 1400/1430 several 
times when I'm using thick paper that is being rejected. It usually 
solves my problem.

Tom Hefter*
>
> >
>
> 



[Non-text portions of this message have been removed]