I have owned an Epson 1500W for about 5/6 years.
I carry out regular nozzel checks every week or two to avoid heads becoming blocked if the printer has not been used.
Today I when I powered up the printer and carried out the nozzel check, the printer first went through an extended cleaning cycle. That's to be expected if the printer has not been used for some time.
I noticed a gap in the printed test image for one of the heads. From past experience, if you leave the printer for a while, the blocked nozzel will often clear itself without running another wasteful cleaning cycle. So I left the printer for about an hour before initiating another nozzel check. The printer unexpectedly decided to execute another extended cleaning cycle before printing the nozzel check pattern.
One of the cartridges was indicating that it was low on ink (the 'ink' led was flashing). However I don't see why this should trigger another cleaning cycle. I sometimes think this is a deliberate ploy by Epson to waste as much ink as possible.
Has anyone else found this issue?
I carry out regular nozzel checks every week or two to avoid heads becoming blocked if the printer has not been used.
Today I when I powered up the printer and carried out the nozzel check, the printer first went through an extended cleaning cycle. That's to be expected if the printer has not been used for some time.
I noticed a gap in the printed test image for one of the heads. From past experience, if you leave the printer for a while, the blocked nozzel will often clear itself without running another wasteful cleaning cycle. So I left the printer for about an hour before initiating another nozzel check. The printer unexpectedly decided to execute another extended cleaning cycle before printing the nozzel check pattern.
One of the cartridges was indicating that it was low on ink (the 'ink' led was flashing). However I don't see why this should trigger another cleaning cycle. I sometimes think this is a deliberate ploy by Epson to waste as much ink as possible.
Has anyone else found this issue?