Re: Samsung CLX-6260FW printer prints blank pages.. most of the time
Just had a look as I'm sure I remember there being some diagrams. It has Circuit Schematics are under Connection Diagram I believe Section 5.2 there are some other diagrams showing where the output sits around the chasis / unit.
I don't really get involved in board repairs, so I don't know what information might be needed that are missing from these diagrams.
It looks like votlage and resistance for individual components are then listed elsewhere. So I'm not sure if that helps at all.
Under troubleshooting I have the below information:
Bad contact on OPC - Check terminal to ground of OPC
LSU not working - Check LSU connector
Not working developing bias voltage on HVPS - replace HVPS
So you are looking at the second section, which is replace LSU/Connector as you checked the connector and that is where the fault seems to be.
I don't think its possible for the mainboard to cause this issue without you getting some other associated error code such as an LSU failure. The only thing loosely related would be if no image is being processed in which case reflashing firmware would fix that.
Just had a look as I'm sure I remember there being some diagrams. It has Circuit Schematics are under Connection Diagram I believe Section 5.2 there are some other diagrams showing where the output sits around the chasis / unit.
I don't really get involved in board repairs, so I don't know what information might be needed that are missing from these diagrams.
It looks like votlage and resistance for individual components are then listed elsewhere. So I'm not sure if that helps at all.
Under troubleshooting I have the below information:
Bad contact on OPC - Check terminal to ground of OPC
LSU not working - Check LSU connector
Not working developing bias voltage on HVPS - replace HVPS
So you are looking at the second section, which is replace LSU/Connector as you checked the connector and that is where the fault seems to be.
I don't think its possible for the mainboard to cause this issue without you getting some other associated error code such as an LSU failure. The only thing loosely related would be if no image is being processed in which case reflashing firmware would fix that.
Comment