SC 672

[keithxxiii]

Hello to all gurus out there,

I noticed a number of SC672-XX calls on the field. Ricoh has a procedure on the service manual how to diagnose it but everything points out to the controller.
Is there a way to check which component on the controller board becomes faulty? I would like to know if we can take those faulty boards and replace those faulty chips would cost us less rather that requesting for a bulk of stocks.

TIA

[TonerMunkeh]

Re: SC 672

In the service manual there are post LED codes that tell you what went wrong with the controller. That can give a PCB repairer of what to replace. Bear in mind, a good chunk of SC672 codes can also be caused by the HDD.

[DRichard]

Re: SC 672

Hello to all gurus out there,

I noticed a number of SC672-XX calls on the field. Ricoh has a procedure on the service manual how to diagnose it but everything points out to the controller.
Is there a way to check which component on the controller board becomes faulty? I would like to know if we can take those faulty boards and replace those faulty chips would cost us less rather that requesting for a bulk of stocks.

TIA

FYI... a bit of a side note concerning this code...

This is from Ricoh's Product Description of the NEW IM CXX10 series of MFPs.

SC672 Isolation Improvement

New troubleshooting flowchart for SC672.

Transport IOB functions are now merged onto BICU.

FFC between BICU and Engine IOB changed to normal harness.

DIMM integrated into Controller.

If enabled, Auto reboot now occurs for all errors, not just for software errors.

[DRichard]

Re: SC 672

FYI... a bit of a side note concerning this code...

This is from Ricoh's Product Description of the NEW IM CXX10 series of MFPs.

SC672 Isolation Improvement

New troubleshooting flowchart for SC672.

Transport IOB functions are now merged onto BICU.

FFC between BICU and Engine IOB changed to normal harness.

DIMM integrated into Controller.

If enabled, Auto reboot now occurs for all errors, not just for software errors.

BTW, upon further review...

The "Improved Troubleshooting" procedure appears to be no more than SC672 indicates a communication failure between the op panel and the controller PCB so the cause of this is either a bad SOP control board, the USB cable or the main control board. (DUH!)

[Matt Sr]

Re: SC 672

On the older 50/51 series, 672 codes were almost always caused by the IPU. Nowadays, most 672 codes I see, are the controller.

[keithxxiii]

Re: SC 672

Ricoh had a good profit margin on those boards.

I had 1 IMC5500, 2 MPC5504, a couple of 3004s in the last 2 months all of them worked fine when controller was replaced.

I did all the POST Codes diagnostics, CMOS and other stuff as instructed in the flowchart but all of those machines got fixed upon replacement of CTL.

[luca72]

Re: SC 672

Ricoh had a good profit margin on those boards.

I had 1 IMC5500, 2 MPC5504, a couple of 3004s in the last 2 months all of them worked fine when controller was replaced.

I did all the POST Codes diagnostics, CMOS and other stuff as instructed in the flowchart but all of those machines got fixed upon replacement of CTL.

I discovered a new thing, I have already solved three times with both controller and IPU, after replacing the customer board, and tried it on a machine in the laboratory, the error actually reappeared, I disassembled the board and washed with alcohol and a brush, and then I blew it well, and the card started working again, I think that given the short time needed for this operation, and the high cost of the card, it's worth a try.

[Gift]

Re: SC 672

I discovered a new thing, I have already solved three times with both controller and IPU, after replacing the customer board, and tried it on a machine in the laboratory, the error actually reappeared, I disassembled the board and washed with alcohol and a brush, and then I blew it well, and the card started working again, I think that given the short time needed for this operation, and the high cost of the card, it's worth a try.

That's interesting, looking forward to the next case now to check that out

Did you scrub it with a brush?

[luca72]

Re: SC 672

That's interesting, looking forward to the next case now to check that out

Did you scrub it with a brush?

yes, very well, in both side, with lot alcool and paint-brush...try

[anothertech]

Re: SC 672

yes, very well, in both side, with lot alcohol and paint-brush...try

I will try this next time too, got nothing to loose if I'm going to replace it anyways.

[luca72]

Re: SC 672

I will try this next time too, got nothing to loose if I'm going to replace it anyways.

Infact, iI did this, because it has worked in the past, in audio electronic enviroment

[anothertech]

Re: SC 672

Infact, iI did this, because it has worked in the past, in audio electronic enviroment

You may find this hard to believe but back in the 80's we used to wash boards in soap and water then hang them to dry overnight. It didn't hurt them. I don't know if I'd go that far today.

[slimslob]

Re: SC 672

You may find this hard to believe but back in the 80's we used to wash boards in soap and water then hang them to dry overnight. It didn't hurt them. I don't know if I'd go that far today.

Back in that time frame I had a state water agency bring in a couple of high end dot matrix printers that they want to know if they could made operational. They had been in storage in a warehouse for a number of years. Took the covers off and found that they had been used by field mice for nesting. Dumped all that nesting and food scraps out, power washed them, rinsed them and blew them dry.They worked.

[Gift]

Re: SC 672

This method also helped me to revive a laptop that ended up in a beer shower during a party back in the days when "Winamp" was popular.

[keithxxiii]

Re: SC 672

Thanks @Luca, I will try to outsource some contact cleaners and spray them. Maybe the humidity in the middle east is a big factor why this boards fail.