SP5210SF with thin lines

[ricmartinho]

Hello everyone!

I'm having very small and thin lines in the feed direction on printouts that have tables. On the 2nd side or if we print only text, the defect almost disappears.
We've replaced AIO, transfer roller, fusing unit, messed with transfer and charge values and fusing temperature. Nothing seems to change this behavior.

Here is an example SP5210.pdf. Zoom in on the top part of the page where it is more noticeable.

Any suggestions?

[FrohnB]

Re: SP5210SF with thin lines

You could Try an HDD. Have had a variety of copy/print quality issues solved by replacing that. What's the total count on this machine? Has there been a toner mess in the past? may want to look at Laser Sync detector, and make sure it's not dirty, but my money is on the HDD.

[ricmartinho]

Re: SP5210SF with thin lines

Hello!

Thanks for your reply.

The total count is +-116k. What do you mean by a toner mess?

I'm at the customer right now and disconnected the HDD but it didn't make a difference.
Will look at the laser and backup the NVRAM to do a NVRAm clear.

I'll keep you posted.

[ricmartinho]

Re: SP5210SF with thin lines

UPDATE

After reconnecting the HDD I can't enter the machine through WIM, just telnet. The Printer says "Please Wait", the Scanner isn't there and the File Transfer tab in System Settings is also missing. No Scanner SP on SP Mode.
I've disabled/enabled Onboard NIC (SP5985-1) and Onboard USB (SP5985-2) and formatted Job Log partition (SP5832-4).
I'm going to fully format the HDD and see what happens.

[FrohnB]

Re: SP5210SF with thin lines

SP 5828-091 needs to be set to "1". Not sure why any of these would have been changed by unplugging the HDD, but I guess weird things can happen. I asked if there was a toner mess (by AIO leaking toner or developer) because they can dust certain sensors/ detectors. Also when you changed 5895-1, did you change it to 1 or 2? I remember having a problem that was caused by that SP being a 2.

[ricmartinho]

Re: SP5210SF with thin lines

Sorry for the late update.
I checked the Controller and harness connections, fully formatted the HDD and I was able to get the Scanner and WIM working again but there are a few SP that have changed. I didn't have time to do a NVRAM clear but my guess is that the NVRAMs are problematic.
I'll keep you posted when I return to the customer.

Thanks

[ricmartinho]

Re: SP5210SF with thin lines

NEW UPDATE

It seems that we have a few more customers (2 or 3) with the same printing issue (thin lines). I didn't go back to the first machine where we spotted the problem to do a NVRAM clear, but with this machines having the same problem, it's less likely to be a NVRAM issue.
We're back to the drawing board analyzing to come up with a conclusion and possible solution.

We'll keep you posted.

Thanks

[JDYAL]

Re: SP5210SF with thin lines

I have a few of these and have had problems with the pcdu's. The quality issues varied, these were brand new out of the box. Since you have the problem on multiple machines try a fresh pcdu. Just a suggestion.

[FrohnB]

Re: SP5210SF with thin lines

Agree with JDYAL. Coincidentally enough, we got a couple of C305 machines from a wholesaler last Friday, and I noticed this exact same problem on the counter sheet that arrived with the machine. Changed Black PCDU and lines gone.

[guitar9199]

Re: SP5210SF with thin lines

If the customer is using aftermarket toner, it's likely the drum units are failing early. Some toner's are more "abrasive" than others.... not mentioning any names though....

[ricmartinho]

Re: SP5210SF with thin lines

I have a few of these and have had problems with the pcdu's. The quality issues varied, these were brand new out of the box. Since you have the problem on multiple machines try a fresh pcdu. Just a suggestion.

Sorry for not posting any update, but I've been away.
It seems like the fault is on the PCDU's. We've changed them and the problem is gone.

Thanks for all your replies.

[JDYAL]

Re: SP5210SF with thin lines

Sorry for not posting any update, but I've been away.
It seems like the fault is on the PCDU's. We've changed them and the problem is gone.

Thanks for all your replies.

Thanks for the update. Glad you got it all worked out.