Yahoo Groups archive

Digital BW, The Print

Index last updated: 2026-04-28 22:56 UTC

Message

Re: Epson clogging/ink waste- Pwr cord pull technique the answer?

2005-06-20 by Phil Rose

--- In DigitalBlackandWhiteThePrint@yahoogroups.com, "Walter George"
<walter.george@p...> wrote:
> Much has been written about the Epson printer head clogging problem and 
> the excessive ink used to keep the heads clean by running the cleaning 
> cycles like Epson recommends. Are there any opinions on the utility of 
> the cord pull technique ?- ie you turn your Epson printer on ( 
> automatic initial head clean which you can't block ), run a head check, 
> you see you have clogged nozzle(s), you then pull the power cord,the 
> print head stays away from from the right pad, you put some Epson clone 
> cleaning solution on the head pad 

Well, what you've described is the good ol' unofficial "standard"
method--recommended countless times--for clearing up clogs in Epson
printers. Sometimes it works...and sometimes it doesn't work. but like
chicken soup: it couldn't hurt.

As to using "some Epson clone cleaning solution"--well I have no idea
what you mean in this context by "Epson clone", however the most
effective cleaning solutions for this technique are said to be
commercial ammonia-containing cleaners, such as the glass-cleaner
called "Windex". The effectiveness of ammonia was established during
the (early) days of dye-ink printers, so I don't know if ammoniacal
solvents are also effective for pigment ink clogs. My 2200 has never
clogged to the extent of needing anything other than one or two
ordinary cleaning (purge) cycles.

By the way, I think that your designation "Pwr cord pull technique' is
not a very good name for this method. It's most commonly called
something like "the Windex method". Of course whatever name is used,
lots of additional detail is needed to describe the method.

Phil

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.