Communications Error with Epson 2200

  • Thread starter Thread starter Jay
  • Start date Start date
J

Jay

I am using an Epson Photo 2200 printer with Win XP Pro and PS 7.01. I
previously had the printer working perfectly although this problem would
intermittently appear and just as quickly dissappear without knowing why.
The printer is hooked up to a Dell 2.4 ghz desktop thru a IEEE 1394
connection. The status monitor will not detect ink levels and gives me a
non-specific Communications error. If I try to print an image, the process
starts, but then ejects the paper 90% empty.

The odd thing is that the printer and computer are obviously talking to one
another since a normal test page can be printed and the nozzle check print
is also normal.

I have already completely removed all Epson drivers from the system and
reinstalled them without curing the problem.

There are numerous posts about these types of problems without any clear cut
cure.

If anyone has any suggestions on how to work through this problem, please
let me know.

Thanks,

Jay
 
Jay said:
I am using an Epson Photo 2200 printer with Win XP Pro and PS 7.01. I
previously had the printer working perfectly although this problem would
intermittently appear and just as quickly dissappear without knowing why.
The printer is hooked up to a Dell 2.4 ghz desktop thru a IEEE 1394
connection. The status monitor will not detect ink levels and gives me a
non-specific Communications error. If I try to print an image, the process
starts, but then ejects the paper 90% empty.

The odd thing is that the printer and computer are obviously talking to one
another since a normal test page can be printed and the nozzle check print
is also normal.

I have already completely removed all Epson drivers from the system and
reinstalled them without curing the problem.

There are numerous posts about these types of problems without any clear cut
cure.

If anyone has any suggestions on how to work through this problem, please
let me know.
Click to expand...

Sounds like a comm problem to me. If you have a spare USB cable, try that
connection. If it works, debug your firewire problem.
 
Jim said:
It is most likely that there is too much of a delay between the sending of
some command or other and the reception of the response back at the
computer. I had this same problem with a 1280 on a USB port which went away
when I reduced the cable length and also made the cable go directly from the
printer to the computer (no USB hub).

You probably have the same trouble.
Click to expand...

Firewire cables can be significantly longer than USB, but I concur that he
has a comm problem. It could be something as simple as a bad cable...it
happens occasionally. Until he tries something else, he won't know.

USB hubs can be problematic. Been there, done that.
 
Also had trouble when I used a poor quality cable, upgraded it to a more
expensive one and problems disappeared.

Ray
 
Back
Top