I'm dying here ...

[Checker]

Not literally, but I have a machine that is kicking my butt and making me look like a fool.

An eStudio 232. The underlying problem is when you turn on the main switch no motors come on ... the scanner does initialize and the panel fires up but as soon as the panel says "wait warming up" it throws an F030 code. This code indicates a communication error between the logic board and the system board.

Originally the call was for a transparency being melted in the fuser unit. I rebuilt the fuser, cleaned out all the hard plastic debris, and now the F030 code appears.

Since no motors fired up my first thought was to check the power supply board. It has no blown fuses nor any obvious abnormalities. Since the logic board drives all the motors except the scanner I decided it was probably at fault. I changed the logic board and the problem is the same.

Finding it hard to believe the scanner and control panel would fire up with a bad system board I didn't go there, so I replaced the power supply anyway. Still the same problem.

I cleared the nvram flags and did a low level partition on the HDD, installed the latest and greatest firmware, formatted the HDD and even though the entire process went without a hitch .. still does the same F030.

I'm at my wits end. Now I ordered the system board even though for the life of me I do not see how it can be the problem. I feel like a dog chasing his tail. All the harnesses involved ohm out ok and the connectors are good. I checked the source voltage and it is a steady 122.8 volts ... a little high but within' requirements.

Whaaaahh. I need that desk job BAD!! Any ideas on this one folks?

[ivovb]

Hi Checker!
It seems to me that You did all the things it should. Anyway I would suggest nvram chips. Use original PCB's but new chips.

BTW 122,8 is too low for Europe.

[tsbservice]

Hi Checker,
Please consider that bad/shorted wires in fuser could blow out old and new boards.
I will try new fuser unit together with power suplly, and next logic board.

Regards

[Checker]

Ok, I'm not only dying here, I'm dead.

So far, NVRAM on both system and logic replaced, logic replaced, system replaced, power supply replaced, fuser replaced. HDD formatted and fresh firmware install. No errors other than F070 (I posted F030 previously in error) when powering on.

I've sent a loaner to the customer and had the machine brought to our shop so it can get gangbanged by all the techs here. If we figure it out, I'll post what it was. I swear this one defies the laws of physics.

[blackcat4866]

Have you tried removing all non-essential accessories? On Sharp products it's usually an accessory that has shorted the 24vdc, killing the whole machine. Just removing the problem accessory usually revives the machine.

And what does a F070 mean? Communication error between ---PWB and --- PWB?

[Mr Spock]

For blackcat4866 It is a failure to communicate between the logic pwb (motor and sensor/switch control) and the System (interface and image control).

I would check the 3.3vdc line. I believe that it what is causing that error. This is cn109 pin b17 on the system pwb to cn309 pin b1 on the logic pwb and cn706 pin 30, cn705 pins 13,14,15,16,19,20 and cn708 pins 9 and 10 on the power supply. Even if the harnesses are good that does not mean the voltage is there. Otherwise I would see about leaving plugs undone until you narrow it down and see what they go to. It could be a bent pin in one socket of one pwb.

[ivovb]

Since both PCBs are replaced I would suggest pressed harness. It is not obligatory to be the harness between two boards, but other one. Mainly strange problems like this come from HVT or fuser harness pressed to machine's chassis(power side).

[tsbservice]

Since the initial problem was fuser related I would think, because system requests the pre-heat start to engine but engine is no response,
pre-heat of heater is not started and system is locked.
Did you check wiring from fuser connectors to LGC board?
Normally it should throw fuser codes, but who knows.

[gptech]

So I thought I would throw in my 2cents here as we just fought with this same issue for 4 months. we also had swapped out all boards and ended up replacing the power supply twice as the original replacement from toshiba was also faulty. Not sure if it will help you but we chased our tails for a long time due to faulty replacement parts.

gptech

[Checker]

Finally got a chance to work on this in the shop and got it fixed. It simply baffles my mind what the problem was. A piece of melted transparency somehow found its way into the recycling assembly and jammed it up. The odd part is that the machine did not give a code for the recycling unit failure, but gave the F070 which as you know led me on a wild goose chase to hell and back. Just for lack of anything else to try I stuck and known working cleaning unit in the machine and it came to ready. So I disassembled the faulty one and discovered the piece of melted plastic. This ain't the first time an error code led me on a wild goose chase, but it IS the first time the problem was that far removed from the given code.

I guess I will live after all.