"4" series developer loss

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • copyman
    Owner / Technician

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

    "4" series developer loss

    I know this has been discussed here many times. Seems to be one of the most common issues lately. Hope the attached docs help explain to anyone searching the fourm for this issue.
    Attached Files
  • blazebusiness
    SanDiegoCopierRepair.com

    Site Contributor
    1,000+ Posts
    • Apr 2010
    • 1246

    #2
    Re: "4" series developer loss

    Originally posted by copyman
    I know this has been discussed here many times. Seems to be one of the most common issues lately. Hope the attached docs help explain to anyone searching the fourm for this issue.
    Thanks , Good info...in my experience people are trying to make those drums go twice or more of their life to save $$$$....we have been able to avoid most of those issues just by replacing the drum units on time and keeping the inside of the unit clean.

    And the 4 series K drums will work in the CMY slots-------and cost next to nothing.
    sigpicAnything can be made to work if you fiddle with it long enough- San Diego Copier Repair.com

    Comment

    • allan
      RTFM!!

      5,000+ Posts
      • Apr 2010
      • 5445

      #3
      Re: "4" series developer loss

      Also agree if its affordable to replace the units. Nice to do on cash calls.

      Different animal on contract.

      When taking drums over life, take them out make sure the grids are clean and rechip them, that would reset aging compensation.

      Thanks for the info. Found the developer getting impacted with toner on low color coverage interesting.
      Difficult one to figure out once that happened. Cure make sure color priority in switched on to use toner on the patches.
      And funny one ask customer to increase color coverage!
      Whatever

      Comment

      • ezzysi
        Technician

        50+ Posts
        • Oct 2008
        • 77

        #4

        Comment

        Working...