MPC6000/MPC7500

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • FASTSTI
    Technician
    • Sep 2009
    • 29

    #1

    MPC6000/MPC7500


    So my 1st question here is what methods have you taken that have successfully worked in this scenario looking for something a little bit more permanent then just force toner, below is an example of the black density change with Its color chart number.
    You just got Pwned by an STI
    Experience Subaru Power
  • scepter2112
    Technician

    50+ Posts
    • May 2009
    • 72

    #2
    Try changing TDC sensor

    Comment

    • FASTSTI
      Technician
      • Sep 2009
      • 29

      #3
      Originally posted by scepter2112
      Try changing TDC sensor
      I will try that but is it not to soon to be doing that? I mean one machine has only 8k on it.
      You just got Pwned by an STI
      Experience Subaru Power

      Comment

      • scepter2112
        Technician

        50+ Posts
        • May 2009
        • 72

        #4
        yes that is weird. But so is copy quality dropping off. There was also problem with Charge roller on other models.

        Comment

        • Scott_Lewis
          Senior Tech

          500+ Posts
          • Mar 2007
          • 519

          #5
          Have you tried reducing the value (pages) in SP3102? If your customer is doing full coverage all the time, change the value to 1 or 2.

          Comment

          • stephend
            Senior Technician

            250+ Posts
            • Apr 2009
            • 306

            #6
            This problem is not only with this model. All new BW models like 6000SP or 6001 have exactly the same problem. Black is fading out after 20 ~ 40 K depends on the coverage. Replacing TD on 6000 didn't help, we have many units with this issue and in my own opinion is caused by a developer production problem combined with the customer's environment (coverage). SP 3102 could help in many of those situations, because forced toner is not a good solution for 6000. Ricoh released new firmware which address this problem, even is not mentioned...they mention it only for one firmware release but every new firmware addresses this problem.

            Comment

            Working...