Hello, we have a Ricoh 5500 installed with one of our clients and it reports SC 672, we have updated the firmware and replaced the board, but after a few days of good work the error gets back, in the service manual it says that is the controller stalled, or installed correctly, but we are an spanish speaking company and dont know what this means, any help will be appreciated.
-
-
Re: Error SC 672 Ricoh 5500
The controller is what runs the machine. here are some possibilities
;
SC 672 Controller start up error - Replace standard memory 256 Part number G3325271 SC 672 Controller startup error - Check damage connection between bcu cn251 and IOB cn227 SC 672 Controller startup error - Insure that system sd card is installed in slot C1 SC 672 Controller startup error - Operation panel PCB defective SC 672 Controller startup error - Poor connection on motherboard cn300 replace PCB SC 672 Controller startup error - Replace BCU PCB SC 672 Controller startup error - Replace CNB board SC 672 Controller startup error - Replace IPU board SC 672 Controller startup error - Replace Network card SC 672 Controller startup error - Replace fuse on controller PSU SC 672 Controller startup error - Replace system sd card SC 672 Controller startup error - Replace transfer unit and IO board as a set SC 672 Controller startup error - replace controller PCB SC 672 Controller startup error - replace controller PSU SC 672 Controller startup error - CN 347 IPU pcb pins bent or connector loose SC 672 Controller startup error - Format or replace HDD SC 672 Controller startup error - reseat System SD card SC 672 replace RAM on controller (G3325721) SC 672 Controller startup error - reseat IOB connectors and ALL memory Dimms
And I will add: put a line conditioner on the power line.
sigpic
You never realize how cheap a professional is until after you let an amateur do it.
A+; Network +; PDI+ -
Re: Error SC 672 Ricoh 5500
Hello, I have more information about this, checking the SP 7403 in the log it shows an error 991, when looking over more detail at the error it shows the next message file[scs:scs_time.count.c] we changed the hard drive for a new one, replaced the main board, and checked the ID sensor that may cause this problem too, also we changed the NVRAM but it keeps sending that error, both 991 and 672, any help?.Comment
-
Re: Error SC 672 Ricoh 5500
Clean the contacts in the RAM DIMMssigpic
You never realize how cheap a professional is until after you let an amateur do it.
A+; Network +; PDI+Comment
-
Re: Error SC 672 Ricoh 5500
We replaced the RAM with another one and it does the sameComment
-
Re: Error SC 672 Ricoh 5500
which do you mean by "Main" board?sigpic
You never realize how cheap a professional is until after you let an amateur do it.
A+; Network +; PDI+Comment
-
Re: Error SC 672 Ricoh 5500
Hi, we mean the big one, where you connect everything, fax, network, sd cards, remember that we are spanish speaking crew, any help will be great.Comment
-
Re: Error SC 672 Ricoh 5500
I would go for the power supply unit, missing some voltage I guess.sigpicWe can all Win, but at the end we all loose. Save the greyhoundComment
-
Re: Error SC 672 Ricoh 5500
Try formatting the HDD in sp mode then 5801 memory all clear, if problem still persists try powering up the machine without the hdd.... if problem still persists i would try a new dimmsigpicComment
-
Re: Error SC 672 Ricoh 5500
We already formatted the HDD and did the 5801 code, also replaced the DIMMS with 2 others that we had here to check for damages, and nothing has changedComment
-
Re: Error SC 672 Ricoh 5500
SC672 . Caused by the small PSU at the base of the controller. You should see a fuse pop on it. Replaced this samll psu with main PSU. Other causes of 672. Interface pcb HDD to controller. 9 time out of 10 = psu on controller pcb part no = AZ23 0198 Power Supply Unit:CTL:EU
good luck
Comment
-
Re: Error SC 672 Ricoh 5500
Had this recently on a Savin 8055. Would not come out of "Please Wait" without SC672.
PSU inside (bottom) of controller box fixed this error. All fuses tested as not blown, but this board was the cause of the error.Comment
Comment