LD533C with E3100 fiery SC672 in mornings

[cobiray]

I've got a D025 that has kicked a SC672 the last 3 mornings in a row. I'm going out to update the firmware again today. I updated the firmware about 5 weeks ago and have had no problem since then with error codes. It also has a Fiery E3100 installed and I think possibly it's a communication issue with the Fiery when it comes out of sleep mode in the morning? Any help or suggestions would be appreciated. The error code screen is over top the copy screen and not grey/blue solid like when you have a bad HDD and it won't boot up, so I don't think it's the HDD. Plus it reboots properly when clearing the code and works for the day.

[TonerMunkeh]

That's an odd one. According to the firmware releases, revision J of the system / copy deals with a 672 related error with the machine receiving a job containing a BW image is stored on the device HDD (e.g. via Locked Print) after the device has just returned from Energy Saver mode, an SC672 error will occur.

According to the Goosey, there might be a problem with the ops panel. Did you do that firmware when you did the other updates?

[cobiray]

I downloaded and put on the latest and greatest of the firmware the last time around. I read that TSB and thought that might be it, but I didn't have any issues installing the firmware like it said. I actually updated it last time since it was throwing sc819's. I'll be re downloading and installing it again later. I really think it's an issue with the Fiery not waking up for whatever reason (bad HDD, needs patched, etc), but nothing jives in the Fiery patches or bulletins either.

[cobiray]

So here's the final chapter.... Stopped out on Monday about 10am and replaced the HDD. Machine had popped SC672 since last visit. Reset code, machine comes up, powered down and replaced HDD, everything seems good. Call comes back Tuesday morning for the SC672, called tech support. Tech support says firmware or HDD. I tell them it's already done with no change, they say controller board. I'm not convinced since the machine resets and runs until it goes into standby overnight. Go back out to reset and check the machine again before ordering the board. Reset code and ran machine. Checked wall outlet with a circuit tester and shows bad ground. Checked outlet with meter and I've got 4+ VAC across the neutral and ground lines. Checked all the open outlets in the place and they all have 3-6 VAC on the neutral ground circuit. I tell the customer and they call the building manager to get an electrician sent over. Line at the main box has voltage on the ground and he says they will have to look into it. Called this morning and everything has been fine since Tuesday when they fixed the issue. I'm gonna stop back for a check up on Monday.

Guess I'm going to have to start checking line voltages a little more closely from now on...

[TonerMunkeh]

Ordinarily you'd have never in a million years thought of that though, or suspected it to be a cause. Kudos for you for finding it tho dude!

[cobiray]

I won't claim I found it on my own. Our manufacturer rep suggested checking it out. He also mentioned the newer machines (color and bigger machines) are much more susceptible to incorrect line voltages and can produce some wacky stuff. Also, there are more details on the logging data report about SC codes thrown. I think it's 7990 that shows it, however there isn't any list available to technicians to decode what it means.

[dfs]

I Had this issue with an af3235c another tech turned off AOF (Auto off ) which is on by default. This got rid of sc672. then i found out that the MFD was sitting on an overloaded circuit which could not supply enough power to bring the machine out of (Auto off) mode.

I tried moving the MFD to an independent power source fixed the issue.

[cobiray]

I installed the original HDD in the machine and printed a logging data report. No error codes since 6-9-11, so everything seems to be all good to go since they fixed the electric. Gotta love the problems that aren't even anything wrong with the machines...

[dawn]

I will try to check the voltage source now if tricky problems happened. Thanks *cobiray* for a great xp.

[cobiray]

Re: LD533C with E3100 fiery SC672 in mornings

So here's an update on this little "gem." Machine worked well for about a month, no reported codes and no glitches to speak of. Then she starts throwing the SC672 and SC819's again randomly. Sometimes it would work for a day or two and sometimes it wouldn't make it to lunch. Replaced NVRAM and EEPROM per our Ricoh rep with no change. Tech support says replace controller boards and BICU next. So it's still not resolved and the condition appears to be worse. Now every time it goes to energy save/sleep it throws a code when coming back on and it doesn't re-establish communication with the Fiery controller so that needs a hard reboot as well. Reloaded the Fiery OS on a new drive and I've got the same thing with no change. Fiery stays online and I can still see it on the embedded web page, so I'm ruling out anything with the Fiery. I'm now leaning towards the controller, but I'm open to other suggestions (hopefully less expensive "guesses"). It's sitting in our shop and I've got the BFH on standby...

[cobiray]

Re: LD533C with E3100 fiery SC672 in mornings

The controller board needed replaced to resolve the issue on the SC672, in case anyone was curious.