Hi, All. I have a C3300 D025 that leaves lines on the scans and copies. It's got a brand new K PCU, K developer is at 11%, and the adf optics are super clean and LD shields are clean. I'm leaning towards an image processing issue, and thought I would see what you guys think before ordering any parts. The test print page actually looks B&W, I scanned all test sheets in color pdf on another good machine so I could post them here.
C3300 Bad Scans
Collapse
X
-
Tags: None
-
Re: C3300 Bad Scans
Hi, All. I have a C3300 D025 that leaves lines on the scans and copies. It's got a brand new K PCU, K developer is at 11%, and the adf optics are super clean and LD shields are clean. I'm leaning towards an image processing issue, and thought I would see what you guys think before ordering any parts. The test print page actually looks B&W, I scanned all test sheets in color pdf on another good machine so I could post them here.Comment
-
Re: C3300 Bad Scans
Pretty sure you've rulled out the engine side ie drum by internal test prints so I'd go into sp4417 iPu test prints 14 or 23 should do.Comment
-
Re: C3300 Bad Scans
What I am seeing comparing the first page, which I think is your original and the next two B&W scans is light streaks that could be the result of dirty optics. At power up when the white reference is scanned, dust in the optics can make the machine think that gray is white and it adjusts it entire gray scale accordingly. Since the color lines only show in the black bands, I am not certain but they also could be from dust that may have a color tinge to it.Comment
-
Re: C3300 Bad Scans
What I am seeing comparing the first page, which I think is your original and the next two B&W scans is light streaks that could be the result of dirty optics. At power up when the white reference is scanned, dust in the optics can make the machine think that gray is white and it adjusts it entire gray scale accordingly. Since the color lines only show in the black bands, I am not certain but they also could be from dust that may have a color tinge to it.
Mika, you say the optics are clean. Does that Include the lens? I've resolved some light streaks like this by cleaning itComment
-
Re: C3300 Bad Scans
Does the problem area enlarge and reduce when scanning ? If it does then it's before the CCD.
You might like to try cleaning the optics with methylated spirits then water.
As a last resort I've removed stubborn insect faeces from the optic mirrors using alcohol.Inauguration to the "AI cancel-culture" fraternity 1997...
•••••• •••[§]• |N | € | o | M | Δ | t | π | ¡ | x | •[§]••• ••••••Comment
-
Re: C3300 Bad Scans
On a couple rare occasions I've had success with reseating the ribbon cables to the CCD. I didn't really think it would help, and I don't think it will help you, but it doesn't cost you anything but 5 minutes.
I tend to agree with slim's diagnosis of colored dust in the optics.
Here's another thought:
eS3555 scanner issue.JPG
You might recognize the Kyocera scanner calibration pattern. This sample came from a Toshiba eS3555 both copies and scans. My customer had been copying books and was pressing hard enough on the glass to snag the light source #1 reflector. The bent reflector blocks the yellow bank of sensors, and the part of the magenta bank, but leaves the cyan and black mostly unaffected.
I think I would spend a little more time with 99% alcohol, cleaning mirrors, CCD lens, and CCD sensor array (only if you can get to it without de-focusing it). I'd also clean and oil the scanner rails, and check that the glides are all there. I'd also re-seat all the connectors involved in image processing.
=^..^=If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
Re: C3300 Bad Scans
Ok, I got it fixed. First off, the good internal print I originally posted was just a fluke. I went ahead and took the LD unit apart and cleaned it which almost fixed it all, but I still had a couple of lines that were vexing me. It turned out to be contaminated developer causing intermittent floating lines. I changed the K dev unit and all was good. I want to thank everyone that replied, and just say I hope you don't have any calls like this one in the near future. It took 3 days to resolution in between running other service calls. If I wasn't completely silver haired before, I sure am now. Is it Friday yet?NEVER ASSUME ANYTHINGComment
-
Comment
Comment