Possible design flaw in developer auger – Xerox Proficio 300 white banding issue

[josep]

In relation to the new Xerox Proficio 300, we are experiencing an issue that appears to stem from a design flaw in the developer feed system. Specifically, the auger responsible for transporting the developer seems to be improperly dimensioned or calibrated, resulting in insufficient supply after high print volumes.

As a consequence, after certain production runs, the system fails to adequately replenish the developer, making it necessary to manually add developer in order to maintain print quality and stability.

The associated print defect manifests as white helical banding, particularly visible on the side farthest from the operator, which further supports the hypothesis of uneven developer distribution across the system.

We have reported the issue to technical service, but the current solution is only corrective and temporary, consisting of manually adding developer into the tank. This requires repeated intervention every few days.

According to the information provided, Xerox is working on a tank modification (possibly an upgrade to the feeding system), but this solution is not yet available.

We would like to know if other Proficio 300 users (or equivalent Fujifilm equipment) are experiencing the same issue, and whether they have received a more definitive solution from the manufacturer or technical support.

 

[SoggyWinter]

If you have a relationship with Katun, you might try sourcing the relevant components through them and see if they are the same, and if they are not, consider hoarding a few augers and/or developer housings until Xerox resolves the issue. Alternately, you could request a replacement of the print engine if Xerox is still doing their satisfaction guarantee.

 

[josep]

I am based in Spain and we have a maintenance contract with Xerox, so they are responsible for replacing any necessary components to ensure the machine operates correctly. The issue is that we have to monitor the machine very closely, because we often leave it running and have already experienced significant waste due to this problem.

They tell us they will resolve the issue, but we are concerned that it may become an endemic problem like the BTR.

This one is even more serious, as it depends on coverage, and the issue typically appears between 10,000 and 30,000 copies.

I mainly wrote this message to warn potential buyers and to find others in Europe who may be experiencing the same problem.