okay folks, here is a puzzler for you...but first some details:
ir8500 - count @ 3.7mil
Drum @ 1mil
Developer Unit @ 500k
All corona units less than @ 100k
NEW DC Controller PCB
NEW Toner Feeder Unit
22 service tech calls for this issue....
Machine has had persistent problem with E020 code, 85% of errors were this code. In conjunction with code, just prior, the image would begin to fade out but the code wouldn't always come up. We could shut off machine for 30 minutes or even just let it idle for a bit and then start up and start copying again. Sometimes for 10, 20, even 30k clicks. Then it would fade again or error out.
All of the new parts (except the PCB) had not prevented the E020 code from coming back. The tech finally tried clearing/flashing the RAM and I've now run 177k without the error. BUT the image has begun to fade out again. I was able to limp along for about 30k clicks running 500 sheets at a time (the job had to be batched like that) and it worked without fading. Now, I can't even do that.
In printing a test sheet (#6) the image is ugly. Pretty faded at one end and streaky. My first thought now is developer unit, but knowing that it has a low count it doesn't make sense to me. (NOTE: this is actually one of two new developer units that have been switched in this machine in an attempt to correct the fading issue and error issue, each has about 500k)
The images that I print are numbers and letters, along the 11" edge of 90# index card stock to make index tabs from. VERY little toner is used on each sheet and I imagine that would equate to similar impact on drum/developer/corona deterioration vs. someone printing thesis all day long.
The DC Controller PCB was replaced once the fading issue returned about 50k ago. Everything was reset/flashed and the new values for the board entered. One value won't 'stick' however. Every time I enter it and I then go back to check, it has changed back to +14 instead of +12, this is the HV-TR > D-PRE-TR value.
Let's see, what else....
New toner has been tried as well as removing all toner from the Developer Hopper. Doesn't seem to make a difference.
Doesn't matter if imaging via copier or printer function.
I look forward to your suggestions. Thanks!
ir8500 - count @ 3.7mil
Drum @ 1mil
Developer Unit @ 500k
All corona units less than @ 100k
NEW DC Controller PCB
NEW Toner Feeder Unit
22 service tech calls for this issue....
Machine has had persistent problem with E020 code, 85% of errors were this code. In conjunction with code, just prior, the image would begin to fade out but the code wouldn't always come up. We could shut off machine for 30 minutes or even just let it idle for a bit and then start up and start copying again. Sometimes for 10, 20, even 30k clicks. Then it would fade again or error out.
All of the new parts (except the PCB) had not prevented the E020 code from coming back. The tech finally tried clearing/flashing the RAM and I've now run 177k without the error. BUT the image has begun to fade out again. I was able to limp along for about 30k clicks running 500 sheets at a time (the job had to be batched like that) and it worked without fading. Now, I can't even do that.
In printing a test sheet (#6) the image is ugly. Pretty faded at one end and streaky. My first thought now is developer unit, but knowing that it has a low count it doesn't make sense to me. (NOTE: this is actually one of two new developer units that have been switched in this machine in an attempt to correct the fading issue and error issue, each has about 500k)
The images that I print are numbers and letters, along the 11" edge of 90# index card stock to make index tabs from. VERY little toner is used on each sheet and I imagine that would equate to similar impact on drum/developer/corona deterioration vs. someone printing thesis all day long.
The DC Controller PCB was replaced once the fading issue returned about 50k ago. Everything was reset/flashed and the new values for the board entered. One value won't 'stick' however. Every time I enter it and I then go back to check, it has changed back to +14 instead of +12, this is the HV-TR > D-PRE-TR value.
Let's see, what else....
New toner has been tried as well as removing all toner from the Developer Hopper. Doesn't seem to make a difference.
Doesn't matter if imaging via copier or printer function.
I look forward to your suggestions. Thanks!
Comment