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
-
Just bringing my 25-cents forth here. With the 4e-series of machines aging out, a lot of them have been coming back in on trades for newer models, I have been salvaging the used development units from them. Any dev unit that comes in under 250K pages gets saved for future use, lower volume ones are preferable obviously. For the machines that are still out in the field that we are trying to get replaced, we don't want to invest a ton of money into them should they all of a sudden need a development unit, so we installed used units into those machines.
Straight up swapping a dev unit can be a crap shoot for sure. Every TCR sensor is different, with different tolerances in the electrical parts on that sensor board. That same sensor will have wildly different TCR readings if you were to swap it between multiple different dev units and copiers, even though those dev units would all have relatively the same toner concentration.
All new, fresh out of the box, dev units should have the exact same toner concentration, +/- a very tiny tolerance amount. The fuse contained in the TCR sensor performs 2 functions, it resets the page counts for the dev unit and forces the copier to calibrate to the new sensor. Yes, the machine calibrates to the SENSOR. The concentration is already at the ideal level in the dev unit (it's new after all), and the copier knows what that concentration is supposed to be. During calibration, the copier is monitoring the output from the sensor, and it records that reading as the baseline for the ideal TCR concentration level.
If you install a different dev unit into the copier, with a different TCR sensor that has different tolerances, the copier is going to see a value that is out of wack with what it was calibrated to. Depending on which way that TCR sensor swings, the copier might try to add more toner to that dev unit to bring the value up to it's calibrated baseline, or it could starve the dev unit of toner because the concentration now reads too high, so it will wait to add toner unit the reading has lowered to it's calibrated baseline. You may also end up with a C255X service code because the reading it is getting from the TCR sensor is so far off, that it thinks the dev unit is either severely under- or over-toned.
How do you resolve all of these problems and utilize a used dev unit? Simple. You swap the TCR chip from the ORIGINAL DEV UNIT that you are pulling out of the machine and install it onto the used dev unit you are replacing it with. Unless you are installing a new dev unit with a new chip, you do not want to use any other TCR sensor in that machine. The copier is calibrated to that sensor, and without that sensor (or a new chip to force the calibration to a new sensor), you will NEVER get accurate concentration readings. The original sensor is "married" to the machine in a sense. Yes, page counts and whatnot are going to be different, but I have never had an issue created by wildly different unit page counts. The problem has always been from using a sensor that the machine was not calibrated to.
Long story short: Take the TCR sensor off the dev unit you are removing/replacing and install it onto the used dev unit you are installing, and everything will work perfectly.A Ricoh Service Tech for 7 year. A Konica Minolta Service Tech for 7 years. Now, KM service manager for 4 years.
My Ricoh knowledge is slowly dwindling away at this point. Many things have been lost to time...👍 3☕ 1Comment
-
Just bringing my 25-cents forth here. With the 4e-series of machines aging out, a lot of them have been coming back in on trades for newer models, I have been salvaging the used development units from them. Any dev unit that comes in under 250K pages gets saved for future use, lower volume ones are preferable obviously. For the machines that are still out in the field that we are trying to get replaced, we don't want to invest a ton of money into them should they all of a sudden need a development unit, so we installed used units into those machines.
Straight up swapping a dev unit can be a crap shoot for sure. Every TCR sensor is different, with different tolerances in the electrical parts on that sensor board. That same sensor will have wildly different TCR readings if you were to swap it between multiple different dev units and copiers, even though those dev units would all have relatively the same toner concentration.
All new, fresh out of the box, dev units should have the exact same toner concentration, +/- a very tiny tolerance amount. The fuse contained in the TCR sensor performs 2 functions, it resets the page counts for the dev unit and forces the copier to calibrate to the new sensor. Yes, the machine calibrates to the SENSOR. The concentration is already at the ideal level in the dev unit (it's new after all), and the copier knows what that concentration is supposed to be. During calibration, the copier is monitoring the output from the sensor, and it records that reading as the baseline for the ideal TCR concentration level.
If you install a different dev unit into the copier, with a different TCR sensor that has different tolerances, the copier is going to see a value that is out of wack with what it was calibrated to. Depending on which way that TCR sensor swings, the copier might try to add more toner to that dev unit to bring the value up to it's calibrated baseline, or it could starve the dev unit of toner because the concentration now reads too high, so it will wait to add toner unit the reading has lowered to it's calibrated baseline. You may also end up with a C255X service code because the reading it is getting from the TCR sensor is so far off, that it thinks the dev unit is either severely under- or over-toned.
How do you resolve all of these problems and utilize a used dev unit? Simple. You swap the TCR chip from the ORIGINAL DEV UNIT that you are pulling out of the machine and install it onto the used dev unit you are replacing it with. Unless you are installing a new dev unit with a new chip, you do not want to use any other TCR sensor in that machine. The copier is calibrated to that sensor, and without that sensor (or a new chip to force the calibration to a new sensor), you will NEVER get accurate concentration readings. The original sensor is "married" to the machine in a sense. Yes, page counts and whatnot are going to be different, but I have never had an issue created by wildly different unit page counts. The problem has always been from using a sensor that the machine was not calibrated to.
Long story short: Take the TCR sensor off the dev unit you are removing/replacing and install it onto the used dev unit you are installing, and everything will work perfectly.
For sure I know techs with decades of experience not knowing how to properly replace used with used developer unit.A tree is known by its fruit, a man by his deeds. A good deed is never lost, he who sows courtesy, reaps friendship, and he who plants kindness gathers love.
Blessed are they who can laugh at themselves, for they shall never cease to be amused.Comment
Comment