[Error Code] Sharp MX-3100N F2-76 and F2-77 codes and jamming...

[The Copy Man]

I have a customer with a Sharp MX-3100N getting random toner CRUM chip codes F2.76 and F2.77. Does this during color print runs, jams then throws one of these codes every time (lately the F2.77 more often).

Here is what we've done so far... Held the "COPY" button down and checked to make sure toners are reading correctly (life %'s all good). Reconnected connections on the PCU board related to the CRUM chips and DV unit sensors, etc, cleaned and inspected CRUM chip receiver sockets (clean and no damage), replaced the Yellow and Magenta toners (they are using OEM), cheated front door, removed toners and made sure toner motors are working and not loose, cleaned Yellow and Magenta DV unit sensors, re-calibrated Yellow and Magenta Developers... What gives? Print quality is great!

NOTE: The machine has been calling for all 4 developers to be replaced and they are past their life's but my fear is to charge the customer $599 for all the developers then have these codes come back. The Drums were all replaced back in September too. But again, the machine is calling for all Developers to be replaced so maybe this is what's throwing the CRUM errors? WEIRD!!

HELP!

Steve.

[SwisSeV]

Re: Sharp MX-3100N F2-76 and F2-77 codes and jamming...

Most likely it's the TC PWB (RDENU0133FCPZ). If it is not mounted correctly onto the frame, electrical noise may occur due to poor contact of the HV springs, resulting to the above troublecodes (and/or constant jam condition). Reseat this board to correct problem.

CORRECTION- That is for the 3110. The TC PWB is different on your model, and it may need replacing instead of reseating.

[The Copy Man]

Re: Sharp MX-3100N F2-76 and F2-77 codes and jamming...

So nothing to do with the machine calling for developers then? That's what I was thinking... leaning for toward the PCU board (Main board?)

Steve.

[copiertec]

Re: Sharp MX-3100N F2-76 and F2-77 codes and jamming...

According to Sharp 1) Replace the toner cart.
2) Replace the PCU PWB
3) Connector/ Harness trouble

I also would address that developer issue as well. It's a catch 22, I would always start with the basics.... First... AC power, next clean and inspect the electrical contacts (which you have done).. make sure none are bent, and the board is in place, then developer, just because that is past due and does need to be changed... and is past the recommended interval, but so is the PCU PWB ( expense wise). So, if the PCU PWB fixes the issue, you still need to replace the developer. Maybe its time for the sales staff to drop by...