mxm365 problem

[bonnie750]

Hello all

I went to a job on this machine which is around 4 months old. original call was for a clicking noise and pcq. fault-finding took me to the main drive assembly and i found the torque limiter for the toner drive was in pieces. i ordered one and fitted it. clicking noise still there! dismantle drive assembly once more and found the coupling pin had chewed the inside of the dev drive. order a coupling. I had a bad feeling about this and inspected the drum drive and pcu, also the dev unit. all looks/feels ok.
ran the machine and it calls F2-40, toner density sensor error.

Paper stops just before the nip of the registration rollers. i checked the sensors for operation , all ok.
i ran toner density setup, no problem there. all motors check out and function ok.
running out of ideas now.i ran aging with misfeed detect off and the machine copies, registration is out by at least 10mm but no code!!!


To be sure i removed the registration ass. and pcu etc, drive unit and rechecked the rotation of the dev unit by taking off the drive train and it feels ok to me.

For the life of me i cant see what is going wrong here, why would the machine be checking toner density in mid copy?

Anyone out there got any ideas?

[bonnie750]

WAZZA!!!!!! the silence is deafening man!!!!!

[OMD-227]

No silence at my end mate..... I've been thinking hard over this one...... my head is hurtin'!!
I read this one over the weekend..... came back to it a few times to re-read it.....and really hoped someone else had seen this, because as of yet, we surely haven't.

As with any of the newer Sharp's, they can definitely throw a F2 code during mid copy..... even on the color MX's.
I'm curious how you had a part inside the main unit that was 'in pieces'. How did that happen? I'm a big fan of Sharp's quality control & all, but that sounds crazy!
Before dismantling anything when you have a clicking noise, did you run sim 6, to try and isolate where the noise was coming from. Running an isolated motor test is always a good idea first off.
So you can run an aging test OK without any errors? Have you run a sim 64 continuous print test? Do you get the error on sim 64?
Obviously with the F2-40 code, that is a toner density error. That can really only mean a problem with toner supply to the dev unit, the dev unit is faulty/not rotating, or the PCU board is bad. If you check the dev unit and there is toner mixed inside, there is no problem with toner supply. Swap the dev sensor if you have another one, or replace the PCU board if you are sure the dev unit is rotating OK.
As for the clicking sound..... I have no idea if I cant see the machine. We haven't really had any calls yet for clicking or unusual noises on the Jupiter2's.
With other MX machines, if the paper stops at the rego rollers, it can mean the machine has a blade flip (that could make a clicking noise possibly - trying to turn the drum), the machine is not detecting a rotating drum (but you would/should get another trouble code) or an image is not yet processed (which could also mean PCU board).

I have read your post over and over....... I'm leaning toward the PCU board for the errors/trouble codes/cq issues, but as for the noise, that will need some thorough diagnostics.

I'm still thinking.........................................

[bonnie750]

Hello Wazza

I thought i could hear a whirring from the far south.....must have been your brain!!

The torque limiter fits on a shaft and controls drive to the toner cartridge. in construction it's much the same as a paper feed item.

the end cap had come off and the helical spring and the centre core were just rattling around on the drive shaft.

I replaced this and tested the machine i found the drive pin had torn away the centre of the coupling...impossible to see unless removed.
when that was replaced it was the first time the machine had run with everything turning under load since the damage was done originally.

running motor tests on the first visit showed that there was something wrong in the drive and on finding the broken part i'm afraid it was a
conclusion waiting to be jumped on!
I cannot run a continuous test as the machine jams everytime.
aging with misfeed disabled allows copies of good quality through.
The customer reckons they had recently changed the toner cart. I thought that if the toner was compacted that could have caused the torque limiter
to come apart but the damage to the drum drive is another matter. we're collecting the machine today and we'll have another look in a workshop.

i'll keep you posted

If the machine runs toner density and process control from the sims without error, how does it call an error during a copy cycle?
Density monitoring is done at a different time as is procon.

Bill

[OMD-227]

Hhhhhmmmmmmmm.............. Still thinking PCU for the Trouble code. I've had similar problems before with MX color machines, in that sim adjustments & dev stirs would be perfect, but immediately show trouble codes in user mode. I just haven't seen this on a Jupiter2 yet, so cant be totally sure. I'm only going off past history with similar engines.
F2-40 would show if the toner drive wasn't working. Have you got another machine in your workshop to change over a dev unit or PCU?

How you got a drive unit to break apart is anybody's guess. I'm impressed.... indeed!

I totally agree in taking this box back to the workshop and working on it properly there. Whats the counter up to?

I just cant get my head around this one. Would love to see it.

[bonnie750]

FIXED!!!!!!!

I didn't have a hand in sorting this one, credit to my service manager, nice one Neil.

Everything was checked again and nothing looked at fault. he ran aging again with dev unit check disabled
for 150 copies. the copies gradually got fainter and he then restarted machine and ran td setup.

m/c came to ready and produced 750 copies.

i've ordered dev and that should be it.....sorted. the original problem with drive unit must have really screwed up
the dev/toner mix. depleting the toner and bringing it back was what was needed.

ho hum you live and learn.

[OMD-227]

Nice one!

I didnt think of that.

Now that you mention it, I have done a similar thing with the MX color machines, where entering secret service mode & entering new value for a particular dev (due to overtoning), then running the machine with solid fill pages to run the toner out of the dev. Once overtoning back to normal, reset secret service mode dev value back to where it was originally. The machine always seems to be OK after that.

Its a similar procedure to what you guys did. Nice one!