Bizhub 601 Developer Change

[ZeusGT]

I am needing to change the developer on a Bizhub 601 and I need to know how to initialize the developer change in service mode. I know how to get into service mode and I also know how to clear the development counter. I just need to know how to to the proper mix after the development change.

Thank you so much in advanced.

[Woxner]

you just need to run the Drum Peculiarity steps. do all of them . drum goes 500k if its due replace it too.

[allan]

For good measure reset the counter as well.
In the manual look for the list of adjustment items.

[copyman]

Yes, make sure to reset dev counter before turning machine off to replace developer. Check dev seals for leaking onto dev gears. If dev gets on the gears they will chew the teeth up quick and result in blank pages because dev not turning.

[allan]

About the dev seals.
At 600K swap the front bushings with the rear ones. That will get you some more life out of the unit.
When the devtank is toast its worth replacing it to avoid dev leaking, toner dumping and background on prints.

Don't think that you really need to do any thing if i understand the machine you can just slap the dev in there.
Always followed the manual, but its a ID controlled machine and should not matter.

[copyman]

Hey allan, nice tip on swapping the bushings. But I disagree with not having to do any calibrations for new developer. Although I have skipped the bias adj in the adjustments I always did the peculiarity adjustments. Even though it uses an ID system it still needs a starting point for developer level. Also this series uses piezoelectric effect and vital to run several pages after setting up developer.

[allan]

Yes agreed, always do drum peculiarity at service time. With my experience with lazy techs it seems to work ok.

[allan]

Piezoelectric effect?
The sensor that makes the funny noise?

[Synthohol]

Tribo effect?
did the 601s have the grid voltage stamped on the drums? been a long time since i saw one.
that was the most important setting to stop spillage, overtoning and saving the fuser roller from damage from build-up on the web.

[copyman]

Hey Syn, haha maybe it was the tribo effect. I remember hearing some weird "effect" that is created with this developer system.

Well whatever it is it sucks and this toner pig will dump toner/dev no matter what you do! As said on here many times this series was a real dog in my opinion. Never met one I liked. They could of solved the main issue of overtoning if they just used a waste box instead of recycling the toner. Don't understand how they thought developer mixed with paper dust wouldn't crash. Lucky to get 100k out of dev that is supposed to last 250k (pm cycle which I think is low for a production model). And they made dealers & customers suffer with this footprint for 10 yrs (5510,600, 601) Never really changing the design or improving any of the issues !!!