This has not been such a problem unit lately for me. I have several of these machines that are only able to go 15k to 30k before needing developer change again. It is way overtoned and dusts all over the inside of the machine. the cq is very shaded as well. I have the all the latest firmware (specifically the engine and system firmware for dusting) I have tried dev units, new drums and blades. tx belts and blades. This is in Minnesota where the humidity is 10% or less. Does anybody have any suggested Sp's or soloutions to help the situation?
mp 6001 7001 8001 9001 developer failing early
Collapse
X
-
Re: mp 6001 7001 8001 9001 developer failing early
I started a thread two years ago with the same issue, really bad dusting. Those same machines arent as bad now. Keep the main filter clean is always a good idea.Do the sp for 'drum condition'. Try to outlive the machine so that you win in the endComment
-
Re: mp 6001 7001 8001 9001 developer failing early
overtoning?? ...as in thick dark raised print, I never see that. see lots of toner where its not supposed to be thoComment
-
Re: mp 6001 7001 8001 9001 developer failing early
There is no solution to this,its just a very bad box. Never sell them, ill be surprised if you make any money on them in the long run.If Ricoh could fix the toner scatter inside the copier it wouldn't be too bad. Until then we are all screwed.Comment
-
Re: mp 6001 7001 8001 9001 developer failing early
Never had any problems with these usually the dev does about 500k which is when I do a full PM.
Make sure the Anti Condensation Heaters are connected to the PSU though as when they are shipped they dont come plugged in the wires and sockets are on the top right corner of the PSU.Comment
-
Re: mp 6001 7001 8001 9001 developer failing early
a common fault with these is actually light copies/prints, follow the bulletins and advice for light copies to get more toner in and it will run cleaner. I think the dusting comes from the dev churning its ars off looking for more tonerComment
-
Re: mp 6001 7001 8001 9001 developer failing early
I have had very good results with these units. Make sure that the ID check interval is set to one, most are set to 10 or 100. Check the dv bias, printing bias bump up and ID bias too. You'll pull more toner out on every page and the patch will be darker so the system will not be as toned. Run and test until you find the perfect balance. The factory setting will not be sufficient in every environment, that's why they make it adjustable. They don't teach this stuff anymore.Comment
-
Re: mp 6001 7001 8001 9001 developer failing early
I have had very good results with these units. Make sure that the ID check interval is set to one, most are set to 10 or 100. Check the dv bias, printing bias bump up and ID bias too. You'll pull more toner out on every page and the patch will be darker so the system will not be as toned. Run and test until you find the perfect balance. The factory setting will not be sufficient in every environment, that's why they make it adjustable. They don't teach this stuff anymore.
The standard setting will check the ID after 10 single copies or at the end of a run of more than 10.
You CAN set the machine to check the ID DURING a run, (Is that what you mean?) but if you set this to 1, it would slow the machine by about half! (Imagine... copy / ID / copy / ID / copy / ID... !)
This setting IS the best way to recover an undertoned machine, set to 10 and run about 150 duplex. (DON'T use "forced toner"! it will overtone) This will normally bring the levels back.
This model is generally VERY reliable and will normally run for at least 350k and up to 450k without a problem if other service parts are changed.
The manufacturer spent hundreds of hours setting these up and the process control setup will try to correct the changes anyway!
P.S
also read
http://www.copytechnet.com/forums/ri...-mp6001-2.htmlComment
-
-
Re: mp 6001 7001 8001 9001 developer failing early
It's because they're shit.
I had a product specialist try to tell me that he's never had a developer fill procedure fail on an MPc6000 or later, although as he ran the course that one of my colleagues was on when it failed then I'm fairly sure that he might have been towing the corporate line on that one.
I've just had to do a developer change on cyan on a machine that had done 20k. Dreadful.Comment
-
Re: mp 6001 7001 8001 9001 developer failing early
It's because they're shit.
I had a product specialist try to tell me that he's never had a developer fill procedure fail on an MPc6000 or later, although as he ran the course that one of my colleagues was on when it failed then I'm fairly sure that he might have been towing the corporate line on that one.
I've just had to do a developer change on cyan on a machine that had done 20k. Dreadful.I think you may have misread the title
There are 10 types of people in this world, those who understand binary maths and those who don'tComment
Comment