This is an odd one for me. Customer put in service request stating that machine was giving them poor image quality. I had them print the built-in demo page and send an image to me. The black portion of the image was not being put on the paper, instead there was some residue on the page that looked like developer. I grabbed a brand new IU-512K and DR-512k and went to the site. TCR density for CMY were all in the expected range, but K was a 0.00%. Replaced the drum and developer as a set(Drum was at end of life, and I've seen issues where these machines will bleed out a developer if you have an old drum, so I figured it was worth doing). Printed some test patterns, and the image was very light. TCR density read normal.
I decided to take the machine back to my shop to work on it. First thing I did was try another developing unit. This time I pulled one out of another machine. Print quality was good, but TCR density showed very high.... like almost 19%. Naturally, the machine coded out every 20 pages or so. I ran some full density half tones to see if the level would drop and the machine would level out, but by the time the TCR sensor was detecting density down to around 12% copy quality was awful. Next thing I tried was changing out the board the developers plug into(A7PUH00500 FRB Board). Flashed the firmware to latest base, and still having the same issues.
Never seen anything like this issue, was hoping for some insite.
I decided to take the machine back to my shop to work on it. First thing I did was try another developing unit. This time I pulled one out of another machine. Print quality was good, but TCR density showed very high.... like almost 19%. Naturally, the machine coded out every 20 pages or so. I ran some full density half tones to see if the level would drop and the machine would level out, but by the time the TCR sensor was detecting density down to around 12% copy quality was awful. Next thing I tried was changing out the board the developers plug into(A7PUH00500 FRB Board). Flashed the firmware to latest base, and still having the same issues.
Never seen anything like this issue, was hoping for some insite.
Comment