MP4000 ligth copy

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • YHEL23
    Trusted Tech
    • Nov 2008
    • 146

    #1

    MP4000 ligth copy

    Hi to all,

    After 100k copy become blurred copy but after i force toner the copy fine in 5k only..I already cleaned the drum unit assy.

    Any idea on this...thanks and happy new year to all..
    DYNAMIC OFFICE SOLUTIONS
  • mikeezoz
    Technician
    • Nov 2007
    • 12

    #2
    Originally posted by YHEL23
    Hi to all,

    After 100k copy become blurred copy but after i force toner the copy fine in 5k only..I already cleaned the drum unit assy.

    Any idea on this...thanks and happy new year to all..

    Hello YHEL23, have you tried cleaning the mirrors in the scanner assembly?

    Comment

    • Shadow1
      Service Manager

      Site Contributor
      1,000+ Posts
      • Sep 2008
      • 1642

      #3
      Sounds like the typical toner problems with these machines - definately change the developer, sometimes the entire developer assy has to be replaced before it will run (sort of) correctly.
      73 DE W5SSJ

      Comment

      • FRIDGEMAGNET
        Trusted Tech

        250+ Posts
        • Aug 2007
        • 377

        #4
        Hot off the press
        There is now a new dev unit available that they say helps to prevent the toner sticking to the mag roller.
        D009 2301

        Comment

        • YHEL23
          Trusted Tech
          • Nov 2008
          • 146

          #5
          Also cleaned all the optic unit.PM for the Developer is 320k.
          DYNAMIC OFFICE SOLUTIONS

          Comment

          • 3bok3bok68
            Senior MFP Technician

            50+ Posts
            • Nov 2008
            • 56

            #6
            Did you tried to clean the Lazer Unit? if yes change the new developer and performed the initialization of new developer.

            Comment

            • YHEL23
              Trusted Tech
              • Nov 2008
              • 146

              #7
              Originally posted by 3bok3bok68
              Did you tried to clean the Lazer Unit? if yes change the new developer and performed the initialization of new developer.
              Hi 3bok3bok68,

              My client only make 100k copies and the developer can copy unto 320k copies.If i force toner the copy become fine for 5k only.....
              DYNAMIC OFFICE SOLUTIONS

              Comment

              • rthonpm
                Field Supervisor

                2,500+ Posts
                • Aug 2007
                • 2847

                #8
                It's not unusual to have to replace developer on this model well before the PM limit. There is an issue with this model with toner sticking to the mag roller and throwing off the settings. Ricoh has put out several bulletins on this issue. Also check your drum ground. Anything higher than 5 ohms and you should replace that as well.
                Start with developer though, also make sure your customer is using the correct toner.

                Comment

                • Shadow1
                  Service Manager

                  Site Contributor
                  1,000+ Posts
                  • Sep 2008
                  • 1642

                  #9
                  Never seen one of these make it to PM on the developer yet. The new assembly helps, but it's not a fix. 100k seems to be the limit before it barfs, but I've been told some accounts only got 15k...
                  73 DE W5SSJ

                  Comment

                  • msaeger
                    Trusted Tech

                    250+ Posts
                    • Sep 2008
                    • 333

                    #10
                    Originally posted by FRIDGEMAGNET
                    Hot off the press
                    There is now a new dev unit available that they say helps to prevent the toner sticking to the mag roller.
                    D009 2301

                    Do you know what bulletin number this is on I can't find it. This one replaces attempt number 2 D0093011 right ?

                    Comment

                    • 3bok3bok68
                      Senior MFP Technician

                      50+ Posts
                      • Nov 2008
                      • 56

                      #11
                      Hi YHEL23,

                      Check the toner hopper maybe the 4 mylar seal remove that why the distribution of toner in developing unit is not enough.good luck

                      Originally posted by YHEL23
                      Hi 3bok3bok68,

                      My client only make 100k copies and the developer can copy unto 320k copies.If i force toner the copy become fine for 5k only.....

                      Comment

                      • YHEL23
                        Trusted Tech
                        • Nov 2008
                        • 146

                        #12
                        Thanks for all the info....I will try it..
                        DYNAMIC OFFICE SOLUTIONS

                        Comment

                        • FRIDGEMAGNET
                          Trusted Tech

                          250+ Posts
                          • Aug 2007
                          • 377

                          #13
                          Originally posted by msaeger
                          Do you know what bulletin number this is on I can't find it. This one replaces attempt number 2 D0093011 right ?
                          From Tessa
                          Attached Files

                          Comment

                          • muratozan

                            #14
                            clean magneticroller

                            Comment

                            • mf02

                              #15
                              hai.

                              i also have this problem but i not replace dev o drum coz still not due only service.i filter the dev and some cases i change mag roller.this method i also used in mp3590/4590 dark,blur & uneven copies.

                              Comment

                              Working...