MP3350 please wait

[nodle]

Initial tech. had please wait and then SC 672. He was unable to access SP modes, the machine was locked up.
Ricoh had him try the BICU. He then got please wait and then SC 670, and was still unable to access SP's.

Ricoh then had him try the Control Board. There was no change in the problem.

Now three calls, and almost two weeks later (I forgot to mention that the machine has only been in the field for three weeks.), I get tagged to handle the fall out. (Of course I can't blame the customer for being upset.)

I went through the manual and also the goose guide. The manual seems to be pointing at the BICU, and the Control Board, and The Operations panel. The Goose Guide had me check the connection between IPU and the SIU, and The connection to the Operations Panel and the MBU. I am still experiencing the same Please Wait message and then SC 670.

I currently have the IPU and the Operations Panel on overnight order. I just wanted to check to see if any of you have seen this problem before, or had any suggestions. Any input will be greatly appreciated. I will be returning tommorrow when my order comes in.

[knightfall]

I've had the same problem on a 5560C and tech support said to replace the controller board, BICU, motherboard, control panel harness as you can guess more parts down the line. What it turned out to be was memory on the controller was oxidized enough to cause the code but not enough to see it on the contact. Try cleaning the contact with eraser then alcohol wipe.

[Brave Hart]

It is your memory that is causing that, rub the contact points with an eraser, or replaces it. We get that for some reason quite often here

[TonerMunkeh]

That's the controller board. I've had a few 2550's do it. Part numbers:

Mono scanner: D019 5310
Colour scanner: D020 5310

I know you've said you've replaced it above but it's been the final resolution for the ones I've had do this. Try and new NVram and HDD when you fit the new controller too. Also, check the jumper settings on the new board, I've had to alter one before fitting it.

[daveyball]

Try unplugging the HDD and switching on, if it works its the HDD

[E Winter]

Initial tech. had please wait and then SC 672

This is a typical SC code for a failes firmware update - you should check if that happened right after an update attempt.

A bad HDD is also possible.

[nodle]

Upon my return to the machine on Friday the first theing I tried was the HDD. There was no change. I then thought I would try the firmware even though I thought it was a shot in the dark, still no change, it didn't even try to do the firmware.

I thought that this just didn't seem right at all, so I decided to retrace the previous tech's steps. I started at the BICU which was the new board he had put in. I figured that I would check the EEPROM legs that some of you have suggested. Low and behold, there it was, or in this case, WASN'T. He had failed to move the EEPROM from the old BICU to the new one.

He will be going out to the account as a first stop on Monday morning, to put the EEPROM on the new BICU. Thank GOD, he hadn't sent the old on in for repair yet.

I will post back to let everyone know the out come.

[nodle]

That was it. The previous tech returned with the eeprom, and that fixed the problem.