new to Konica if copier has a bad developer unit and you replace it with a known good one will copier work or do you have to install a new developer chip .
Konica Minolta question about developer units
Collapse
X
-
Swapping used developing units is generally not a great idea. You cannot do a proper developer stir, so toner density won't maintain. The counts will be off. Color calibrations are based on those counts ... all these things mean that even if the developing unit was good, you can't do a proper calibration, so it won't maintain quality.If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=👍 3Comment
-
I've swapped developer units dozens of times with no issues. Sometimes you may need to get the levels right by manually adding some developer (aftermarket) or toner. Once stable do gradation adj and should be locked in and ready to go.Comment
-
Let us eat, drink, and be merry, because tomorrow we may die!
For all your firmware & service manual needs please visit us at:
www.copierfirmware.co.uk - www.printerfirmware.co.uk
​👍 1Comment
-
And I can't be that lucky with all the dv units I've swapped and no issues.Comment
-
Interesting thread.
I still have a fair few 4e devices in the field that love to emtpy their Cyan Devs even when the TCR value is within spec.
Any time I have swapped a dev from a known good workshop machine the recipient machine will always report the new Dev as 0% TCR and throw the C25xx code after a few prints. The only way I have resolved this is to ensure the dev was correct in the good machine i.e TCR in spec, then swap the dev chips.
These are all runing GDR-M1.
If someone has some insight into how to get the TCR value to re-register aftrer swapping that would be great, I could be missing something totally obvious in the swap process!
Comment
-
Interesting thread.
I still have a fair few 4e devices in the field that love to emtpy their Cyan Devs even when the TCR value is within spec.
Any time I have swapped a dev from a known good workshop machine the recipient machine will always report the new Dev as 0% TCR and throw the C25xx code after a few prints. The only way I have resolved this is to ensure the dev was correct in the good machine i.e TCR in spec, then swap the dev chips.
These are all runing GDR-M1.
If someone has some insight into how to get the TCR value to re-register aftrer swapping that would be great, I could be missing something totally obvious in the swap process!Comment
-
The 4E models are the most I've swapped dev units in. I was always able to get the levels to 6-6.5% without chips. When I did try chipping a used DV unit I had issues so just swap them out. Like I said there are times I have to manually tone up to get levels right but other than that used units work great! Save the $500......Comment
-
The copier I am working on is a bizhub 405i. Had Blank copies. swap drum and black develop unit now image is very very lite and in some spots fills like developer powder. in service mode hit caution symbol display front id sensor problem and developer and drum problem.Comment
-
Never had a problem swapping DV Units, but have only done it for troubleshooting on the 4 series, which is what others have said, it empties (mostly) the Cyan developer. I've even used the generic Developer to refill it with, with no issues. Most generic developers come with the reset chip, so you just have to replace that along with the new powder. Kinda messy, but has always worked for me.
OC👍 1Comment
Comment