[Misc] Konica C280 image

[mearmi]

Please find the attached image.

replaced the developer unit K. It worked fine for 2 days. Again got the same problem.

please advise.

Thanks and kind Regards,

[blackcat4866]

Re: Konica C280 image

It's definitely developing. Are you using generic toner? Maybe the toner hopper is backed up.

Obviously it's undertoning black. =^..^=

[danetime]

Re: Konica C280 image

I would go for hopper unit. The black toner on those models contain toner and carrier. I've had a few issues where the hopper drive get tight causing lack of toner and carrier to dev resulting in this issue.

[mearmi]

Re: Konica C280 image

It's definitely developing. Are you using generic toner? Maybe the toner hopper is backed up.

Obviously it's undertoning black. =^..^=

Thanks for your reply.

Yes we using katun Toner.

shall I vacuum the hopper unit?

[JR2ALTA]

Re: Konica C280 image

The toner is the problem. If you want to pursue a solution other than that you're on your own.

[femaster]

Re: Konica C280 image

Even using generic toner, your dev unit should not be empty after 2 days.

Long Story Short:
If the toner hopper cleaning doesn't help out the situation, check the drum life, if EOL, replace it at the same time as the dev unit.

Long Story:
We have a C280 with a similar problem (we do use OEM toner BTW) where we replaced the K dev unit for the diagonal void bands due to dev unit being nearly empty. After a few days the dev unit was empty again, it had emptied itself into the waste toner box. There was never any evidence of developer on the copies/prints.

After having to put in a second dev unit, we replaced the drum at the same time (it was end of life anyway) just to see if that would help. The copier lasted about a year after that, when it happened again; diagonal voids and K dev unit nearly empty.

By that time we had forgotten about the previous issue and solution, so the dev unit was replaced by itself, and a few days later, got a call for the void lines again. Looking at the history, noticed that the solution was replacing the drum at the same time. The drum was in fact at end of life again, so we did both again, and it's been running perfectly since. Now, we just monitor the life for the K drum and replace it when it's near end of life. We have not had another problem with developer dumping since.

We've only had this happen on 1 machine of the approximately 50 machines from this family that we have out in the field. Not really sure what is causing it to act this way, but replacing the drum at EOL is easier and cheaper to deal with than randomly replacing boards to try to resolve the problem, which may not even fix it.