Ricoh SC 672 - controller communication error
Communication between the machine's controller board and the operation panel or engine was lost or never established at start-up. The machine typically shows the code shortly after being switched on and does not reach the ready state. It is a controller-level fault rather than a printing problem.
What causes it
- The controller board failed to start correctly
- A loose or damaged internal cable between the controller and the panel
- A firmware fault or interrupted update on the controller
- A failing optional card, memory module or internal storage device
- A power interruption during start-up
How to fix it, in order
Work down the list and stop when the printer recovers. The steps are ordered from most likely and least invasive to last resort.
Switch off and wait before restarting
Turn the machine off at the main power switch, wait a full two minutes so the controller discharges completely, then switch it on. Give it several minutes to start, since a controller performing extra checks takes longer than usual to reach ready.
Plug directly into a wall socket
Remove extension leads or power strips and connect the machine straight to a wall outlet. A power interruption or brownout during start-up is a plausible trigger for a controller communication failure, and removing that variable is quick.
Disconnect the network and any USB devices
Unplug the Ethernet cable and any connected USB storage or accessories, then restart on the bare configuration. If the machine reaches ready this way, reconnect items one at a time to identify what prevents start-up.
Remove optional cards
With the machine off, remove any optional interface card, wireless module or additional memory and restart. An accessory that has failed can hold the controller's communication bus and prevent the panel initialising.
Note whether the panel responds at all
Record whether the panel is blank, lit but frozen, or showing the code with a working display. That distinction tells a technician a great deal about where the communication is failing, and costs nothing to observe.
Record the code and arrange service
Note the exact SC number, model and serial number from the machine's label, along with anything that changed recently such as a firmware update or a power cut. Controller faults require service-level diagnostics and often a board or cable replacement.
Stopping it happening again
When it is not worth fixing yourself
If you would rather not work through this alone, a printer specialist can take a look with you on a screen-share and tell you honestly whether the machine is worth saving.
Printers that show this code
Frequently asked questions
Can I still print while SC 672 shows?
Usually not. The machine does not reach a ready state, so jobs sit unprocessed on the sending computers.
Did a power cut cause this?
It can. Interrupting the controller during start-up or during a write to storage is a recognised trigger.
Will my address book survive?
Usually, since it is stored separately, but a failing storage device puts it at risk. Mention it to the technician.
Questions & comments (0)
No comments yet. Describe your printer model, operating system and the exact message you see; comments appear after review.
Ask about this page
Your comment appears after our team approves it. Or sign in to post faster.