IR8500 Print/copy blank

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mezerwi
    Technician

    Site Contributor
    50+ Posts
    • Aug 2010
    • 58

    #1

    [Misc] IR8500 Print/copy blank

    Hi,

    Problem: The copy is blank

    Situation lead to this problem:
    Doing normal 2 sided copy and suddenly jammed. Paper stuck at drum. Remove paper and resume copy. Lines appear at 1/3 side of the copies and after several copies, output blank. Check primary charging, toner appear at 1/3 end side of the primary charging unit as well as on top of the drum.

    Changed the whole drum unit with reserve 7200. Test print, output blank.

    Checked where the problem, by halting machine process when paper passing under the drum. Remove jammed paper and swipe under the drum with soft tissue. No toner trace detected.

    Double check the output to define the blank: 5-10% faint toner detected.

    Checked the primary charging, replace with other set, problem still exist.

    So guys, what should i check next?

    Mezerwi.
  • teckat
    Field Supervisor

    Site Contributor
    10,000+ Posts
    • Jan 2010
    • 16083

    #2
    Re: IR8500 Print/copy blank

    VL1M and VDM - check target values
    is resistance measured from the hvt to the end of the developing cylinder
    is DEV_DC CNTR signal present from the DC controller J510-A9 to the hvt at J723-8
    check if developer bias is present at the end of the mag roller,when checked with a multi meter
    **Knowledge is time consuming, exhausting and costly for a trained Tech.**

    Comment

    • mezerwi
      Technician

      Site Contributor
      50+ Posts
      • Aug 2010
      • 58

      #3
      Re: IR8500 Print/copy blank

      Thanks teckat,

      Problem solved. Bad connector on developer unit. [those single cable]

      Comment

      • teckat
        Field Supervisor

        Site Contributor
        10,000+ Posts
        • Jan 2010
        • 16083

        #4
        Re: IR8500 Print/copy blank

        Originally posted by mezerwi
        Thanks teckat,

        Problem solved. Bad connector on developer unit. [those single cable]
        Case Closed.JPG
        **Knowledge is time consuming, exhausting and costly for a trained Tech.**

        Comment

        Working...