MX2300N Call for service code F2-65

[Guest]

What does this service code mean and is it something that we can check on first ourselves?

[Si@danwood]

Issues with the process control are you a tech or end user?

[jazzfanatic]

I just help out occasionally with IT projects (networking, printers, etc) here at my business. I am somewhere in the middle between a service tech and end user.

[Si@danwood]

Well i am not 100% on the exact cause of this as i do not have the correct manual to hand but you will need some technical training/resources to rectify this paticular issue as F2 codes on Sharp kit(as i recall) genarally refers to Process control issues..Si

[jazzfanatic]

I don't think it is necessarily the process control, because on this same forum the f2-64 code was listed and it was said to be the Bk Toner supply.

[JustManuals]

This Parts & Service manual can now be purchased for $11.77 and downloaded immediately after payment
from http://www.justmanuals.com


Paul@justmanuals.com

[ZOOTECH]

F2-65 is the Cyan toner supply abnormality; could be caused by a blocked toner transport pipe from the toner cartridge to the DV unit.

[Nachoman4life]

more than likely the toner cart was stored upright instead of flat, and was not shook when installed, hence a large mass of toner on one side of the cart that the stirring parts and augers cant overcome. Or a blocked toner pipe, (although these are very rare for me) Or the drive gears and belts on the rear frame of the developer unit are skipping(or worse broken, if its skipping you will see it in the copy quality, and probably hear it) (Happens more often on black), if they are, a full tear down and cleaning of all bushings bearings and shafts is probably needed (high count machines usually need this around 1.5 mill.) If you aren't a trained tech do not try to do any fixes, other than trying a second well shook cyan cart, past that call a trained tech

[jazzfanatic]

Well, it was the cyan toner, and it appeared whoever installed it only took off a piece of the tab. Simple fix obviously, just strange the problem didn't show up until now because that was apparently replaced a long time ago. Thanks everyone.

[NotByChoice]

For future reference:

I had the same Code:F2-65. on a MX-5001N copier and the solution was replacing the Waste Toner Box. I tried shaking the cyan several times and it didnt help. Then I noticed that the Waste Toner Box was overflowing cyan so I tried replacing it and when I turned the copier off/on the code went away!

[OMD-227]

That is unusual....

The WTB has nothing to do with this, or any code.

That code is toner supply abnormality. As already mentioned above, its usually a blocked toner pipe, sealing tape still on the cartridge or toner has become hard in the cartridge due to incorrect storage. The WTB has nothing to do with this.
How could you tell if the WTB was overflowing with cyan only? If the WTB was full, it would trip the waste toner motor clutch.

[NotByChoice]

There was cyan toner that was all over the outside of the WTB. Could it be that the waste cyan was clogged leading to that code? I don't know much about the Sharp machines to be able to say that it was 100% the WTB. All I know is the last thing I tried was changing the WTB so I assumed that did it :P

[OMD-227]

If you have any toner covering the outside of the WTB, it is almost for certain, that there has been toner spilt from a new cartridge when installing it. It always tends to fall down over the area below the toner cartridges..... right over the outside of the WTB. I'd say that it was a very poor attempt at installing a new cartridge, rather than a WTB fault.

If you didnt check the toner pipe, shake the crap out of the toner cartridge, confirm the dev unit drive belt is OK and not seized up and the tape is fully removed from the cartridge, then it just might come back.

However, something to keep in mind..... If the client has been removing & inserting that toner cartridge (and toner dropping out of it in the process), there is a chance the CRUM chip has blown or the cartridge was not 100% installed fully, eventually leading to the toner supply trouble code.

If everything is seated OK, then it should be OK. One way to confirm toner is flowing correctly again, is run solid cyan pages through it in sim 64-01. Change A to 1, select C for cyan, select multicopy and run it continuously. The machine will pause for a few seconds when it is replenishing toner. If it continues OK after this small pause, then you know toner is flowing OK between the cartridge & dev unit.

[NotByChoice]

Thanks for the tips. I'm the IT Manager for the office so I have general knowledge of everything but not specific enough to do all of the troubleshooting advice you gave. There's some cyan lines at the top of some pages but I think that's because the drum+dev are over 100k now. I have a tech coming in to change those so I'll get him to check out the things you mentioned while he's here on the clock.

Thanks again

[OMD-227]

Just an update on this code (and associated F2-64, 66 & 67).

Had 2 calls yesterday with this trouble code, with the exact same cause, not mentioned here on this post as yet. I know this post is already closed, but maybe this extra info might help someone in the future.

Both machines were low page count, high drum rotation machines in a hot room. F2-65 error constantly appearing each startup. Found the CMY drums so badly worn on the rear frame that bare metal of the drum surface was so exposed that it had actually cut a deep ridge into the aluminium. The deep ridge was full of developer and was causing a massive drum surface potential increase & constant charging of the drum. This was constantly pulling toner as the machine was feeding toner in.
As usual, after the process control timeout, the error appeared, showing that there was a 'toner supply abnormality', whereas infact, the toner was supplying perfectly fine but the developer was unable to come to ready due to toner constantly passing through to the badly worn/damaged drum.

Funny part was, the developers were OK. Usually when there is excessive toner pull from the developers, the dev usually goes with it, eventually emptying the dev unit and straight into the waste toner box.

3 new color drum units as required, color calibrated and all back to normal. Confirmed all other causes of this problem were OK. Confirmed toner replenishment sequences OK during long high coverage print runs.

Moral of the story........... Check the drums (even if clean & low page count) as well as the usual toner pipe, toner cartridge, developer drive belt and toner coupling which primarily cause this code.