Ricoh AFICIO 2228C

[LaserSharp]

This is a Lanier branded unit, I did not have time to look at it very hard, but the customer says it was working until they pulled the drums to clean...(do to print quality I guess they thought it was a good idea).

And now upon powerup the system comes up with a code "sc 393-04" I will probably be back there tommorow to finish work on another machine and will have time to check it out more, (it was also recently moved) but in the spirit of being dead tired after a long hard day, I thought I'd throw this up.

[JustManuals]

This Parts & Service manual can now be purchased for $11.77 and downloaded immediately after payment from The Internet's largest collection of manuals


Paul@justmanuals.com

[Fearless V K]

SC 393, TD sensor error during warm up

Try reseating the developer units and make sure the positioning plate it not out of place. Also make sure the customer did not knock any of the TD sensors off of the developer units.

Hope it's a chargeable call.

[zedreckon]

Had the same problem with my 2228C after getting via a courier some used developer units. After a cleaning them and mounting them in the unit SC 393. I started up the copier a few times and no SC after that.

[Eric1968]

"They pulled the drums to clean." ????? I would advise your customer to stay away from cleaning drums.

[E Winter]

Try and bend the lock lever wich is securing the Drum/Dev Units a bit "banana shaped" (that brown thingy in the front where you must loosen 2 screws and lift it up). That prevents too much play for the units in the middle - especially the dev units tend to have an almost loosen connection in the backside of the machine.

[Llama God]

I'll narrow it down a bit, it's the magenta dev unit.

Cheat the front door, turn the power on and push the magenta dev unit in whilst the machine initialises. If the code comes back then, I'd try a replacement dev unit and charge the customer an idiot tax.

[blackcat4866]

I'll narrow it down a bit, it's the magenta dev unit.

Cheat the front door, turn the power on and push the magenta dev unit in whilst the machine initialises. If the code comes back then, I'd try a replacement dev unit and charge the customer an idiot tax.

Definitely billable. Plus the admonishment that fixing it yourself can get really expensive in the end.

[Llama God]

In fact, just ring them back and tell them to fix it their bloody selves!

[teebee1234]

A possibility that they vacuumed the developer off the mag roll if they went in there to 'clean' it (seen it done before). May have done it to all of the dev units, but can only show 1 error at a time.

[Llama God]

A possibility that they vacuumed the developer off the mag roll if they went in there to 'clean' it (seen it done before). May have done it to all of the dev units, but can only show 1 error at a time.

Good call! Turn the dev unit(s) manually and check that they each have a good brush.

[XXX]

A possibility that they vacuumed the developer off the mag roll if they went in there to 'clean' it (seen it done before). May have done it to all of the dev units, but can only show 1 error at a time.

No way.
The customers are too lazy to vacuum all the dev units and besides, they would have quit after the first static discharge jolt.

Chargeable call = replace components