It looks like the grid on the primary charge corona was not secured on one of the tabs ...the end result being all the magenta dev has been sucked out of the dev assy...since these machines are supposed to "never" require new dev, is the developer material available separately? I am assuming it has to be and you would just replace it like any other machine? . I was able to get a few pages out of the machine till it finally crapped out with a CA00,so it should be ok with new mag. dev....if you have a part# that would be great help as well! I believe it is FC55M?
-
-
Re: 5520C Error code ce40...no dev left in the dev assy
D-FC55-M 6LH16883100 very pricey at more than $300 -
Re: 5520C Error code ce40...no dev left in the dev assy
Also there is a procedure to follow. kind of like the old 310/311 series machines. Follow the service manual. It is NOT the kind that just dumps in.
Comment
-
Re: 5520C Error code ce40...no dev left in the dev assy
Make sure there is no tiny crack in the Dev unit that allowed all of the Developer to run out. This happened to one of my techs last week.Comment
-
Re: 5520C Error code ce40...no dev left in the dev assy
Check the developer drive properly, my colleague did encountered a white color gear broken resulting toner not able to get into the developer units thus drain the developer material.Comment
-
Re: 5520C Error code ce40...no dev left in the dev assy
First thing to check is all the EPU connections for HVTsprings and drawer connectors and make sure the EPU is going in smoothly.
2nd check the performance index in PM Supportmode to see what the developer threshold is at. An average number is around 20.If it is close to 100 that means the developer is not being used enough tore-plenish properly.
Comment
-
Re: 5520C Error code ce40...no dev left in the dev assy
It could be the spring contacts. If it is only happening with Magenta, switch the EPU units with Yellow or Cyan to test. This will eliminate problems with the EPU unit itself. If the problem does not transfer with the EPU unit, then you would be looking at either, contacts, possible dirty Vo sensors, and what about the TransferBelt unit. It could be causing some arcing as well. Make sure to check this assembly as well. Did you recently service the developer unit and this started happening afterwards, or was the original problem no developer in the dev unit? Make sure no developer material has spilled down onto the Laser unit.
It may be a good idea to remove and re-install the problem developer unit in case it is slightly out of position. It must sit flat not angled when properly installed. If it was previously disassembled make sure that it was reassembled properly with no parts missing including the 2 springs and the overflow spout wire. Make sure the Black plastic cover is mounted properly as well.
Are there any other errors or messages appearing or just CE40? Make sure to not forget to clear any detection abnormalities in 08 mode(573-576) back to 0.Comment
-
Re: 5520C Error code ce40...no dev left in the dev assy Update....
Got the dev finally ,put it in ...got a couple of c447 codes(?) while trying to run 05 202 ...had to pull out all the cassettes before it would go...it let me add the dev no problem...until I get to run 05 396 and it gives me a magenta error when I check it in 05-2780 the error is a 2 ...in 05 2789 its a normal 0....however it let me calibrate in user mode no problem. I have swapped the EPU and the potential sensor assy with the cyan and it still gives me an error if I try to run 05 396.Copies are great I had replaced the drums and EPU kits at the same time. I didnt see any obvious issues with contacts ,springs,connectors etc.Ran out of time last night but I will go back this afternoon and see if I can find anything.....Comment
-
Re: 5520C Error code ce40...no dev left in the dev assy
Just a follow up for those that were following this thread, heres what transpired when I went back to tha call, because of the error codes I did not realize that the machine had disabled the drum potential reading,which I assume is why I saw no change when I swapped the sensor assy between the magenta and cyan.After I turned it back on however the error code had moved to cyan.To confirm the potential sensor was at fault I moved it back to cyan and....no error! Swapped them again, still no error,put them back in the original locations still no error. All I can assume is that it was connector related? to the potential sensor assy. Its been almost a month and we havent had any service calls on the machine so I am going to assume its gonna stay fixed lol!Comment
Comment