Recent content by IanYY

The MG5300 is functionally very similar to the MG5200 series - the MG5300 supports AirPrint and has a slightly different body shape, but that's about it. So this user manual for the MG5200 applies (nearly) equally to the MG5300 ...

I can't comment on the HP LBP6020, but historically HP lasers have shared Canon components, as stated by Lukasz. See the first couple of paragraphs of ... http://en.wikipedia.org/wiki/HP_LaserJet

Your problem could be due to a poor quality wireless connection between the printer and the router, causing signal dropouts. You can check the signal quality using Canon's "IJ Network Tool". This may be installed already on your PC (Try Start -> All Programs -> Canon Utilities -> IJ Network...

It's very suspicious that the guy I bought it from advertises on Ebay ... A4 self-adhesive glossy posters Printed cake topper icing sheets Printed cake topper rice paper A4 printed iron on fabric transfers I might guess that the "edible ink" was the cause. Ian

FIXED. But first a bit of background ... I bought this as a "faulty, spares or repairs" printer, so it's not surprising I've had some problems with it. And I have no knowledge of its previous history. Fault #1. Wouldn't power on, with a 5B00 error code (Ink Absorbers Full). Fault #2. Wouldn't...

My MG5350 mainly prints OK, but has a line feed problem at the bottom of every sheet. I've attached some photos to show the problem ... 1. This photo, and all the others, just show the bottom corner of each sheet, about 50mm (2 inches) in height. This one is printing a grey block on plain...

To guess an answer to my own question (only a guess). Maybe the purge pump was weak - it could suck enough to pass the purge test but wasn't sucking hard enough to pull ink through the head. Maybe the cleaner applied during the purge tests eventually cleared something and improved the suction. Ian

Check your purge pump using the instructions in post #1 here ... http://www.nifty-stuff.com/forum/viewtopic.php?id=4569 Note that some printers seem to need turning off and on again at step 4 rather than just closing the lid (though the MG5250 doesn't need this extra step). My MG5250 had a...

Well ... I tried the vigorous rub with a Windex-soaked cloth and this is what I got ... It's a bit different - the overall effect is worse! The top few lines of the magenta bar are still hardly visible, and the bottom few lines are now missing completely. The offset to the right is worse on...

1. Is the paper moving up and down while the printhead does its 9-10 movements? If so, websnail's suggestion is correct and the printer is attempting to straighten the paper before starting to print. 2. If the paper is not moving (and there NO noises and pauses at the end of each stroke...

I think this might be worth a gamble. The printhead nozzles have already been stood/soaked in Windex, but I have been very wary of direct physical cleaning of the nozzles (apart from a gentle wipe when drying the printhead). Next week (next time I will have an opportunity), I will try wiping...

I noticed spike marks on photos printed with my MG5250 when it was new, but the marks not visible at all now. I think the sharpness of the spikes has just worn off a bit with age. Alternatively (just guessing), you could try slowing the printer down to give the ink more time to dry before it...

After a bit more investigation, I think I have to agree with Stratman and Hat, and accept that this is a printhead problem. I tested the printhead in a spare ip4700 (which has a different printhead fault), and the fault moved to the new printer ruling out the logic board and the timing strip...

{Edit} Canon ip4700 {/Edit} Image 1 shows the problem I am having with Magenta - lighter coloured stripes when priinting blocks of various shades of Magenta. All others colours print OK. Image 2 shows the cause. This is a magnified extract from the Service Test Print (which shows the problem...

I had a similar issue, described here ... http://www.nifty-stuff.com/forum/viewtopic.php?id=4705 ... (sorry the photos have gone AWOL, and ignore my first wrong suggestion that this was a software problem). Definitely a faulty printhead in my case. It would be worth running the service test...