Konica Minolta question about developer units

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • COPIERMAN
    Senior Tech

    500+ Posts
    • Jun 2009
    • 559

    #1

    Konica Minolta question about developer units

    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 .
  • 4Toon
    Trusted Tech

    100+ Posts
    • Mar 2023
    • 104

    #2
    Originally posted by COPIERMAN
    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 .
    newer models it should just work. What is your issues?

    Comment

    • blackcat4866
      Master Of The Obvious

      Site Contributor
      10,000+ Posts
      • Jul 2007
      • 22929

      #3
      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 =^..^=

      Comment

      • copyman
        Owner / Technician

        Site Contributor
        2,500+ Posts
        • Sep 2005
        • 4524

        #4
        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

        • copyrooks
          Trusted Tech

          Site Contributor
          100+ Posts
          • Oct 2013
          • 207

          #5
          I wouldn't, you run the risk of error codes like C25xx, the potential of causing more damage or cleaning up a huge mess when you finally go back to replacing the unit properly.

          Comment

          • copier tech
            Field Supervisor

            5,000+ Posts
            • Jan 2014
            • 8101

            #6
            Originally posted by COPIERMAN
            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 .
            Yes been doing this for years without any issues. No need to replace the chip that would do more harm than good.
            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

            ​

            Comment

            • copyman
              Owner / Technician

              Site Contributor
              2,500+ Posts
              • Sep 2005
              • 4524

              #7
              Originally posted by copyrooks
              I wouldn't, you run the risk of error codes like C25xx, the potential of causing more damage or cleaning up a huge mess when you finally go back to replacing the unit properly.
              Not sure what you mean by mess? I've never had a mess from 255x codes. It's not like it dumps developer the way older machines use to. If anything the developer would go into waste box.

              And I can't be that lucky with all the dv units I've swapped and no issues.

              Comment

              • Slammers
                Trusted Tech

                100+ Posts
                • Feb 2019
                • 104

                #8
                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

                • doinbox
                  Service Manager

                  50+ Posts
                  • Jan 2013
                  • 67

                  #9
                  Originally posted by Slammers
                  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!
                  TCR wil be wrong until you fit a brand new dev chip in the used Dev unit.

                  Comment

                  • copyman
                    Owner / Technician

                    Site Contributor
                    2,500+ Posts
                    • Sep 2005
                    • 4524

                    #10
                    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

                    • Slammers
                      Trusted Tech

                      100+ Posts
                      • Feb 2019
                      • 104

                      #11
                      Originally posted by doinbox

                      TCR wil be wrong until you fit a brand new dev chip in the used Dev unit.
                      Excellent , was just making sure I wasn't missing something here. This is what I've always had to do.

                      Comment

                      • COPIERMAN
                        Senior Tech

                        500+ Posts
                        • Jun 2009
                        • 559

                        #12
                        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

                        • Oystercopy
                          Senior Tech

                          Site Contributor
                          500+ Posts
                          • Oct 2009
                          • 617

                          #13
                          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

                          Comment

                          Working...