I'm getting a ppd_pri jam code on an arm550n. I've replaced the toner seals in the process unit, per sharp's tech bulletin on the subject, and replaced the M/C unit, cleaned off all the vertical feed tires and checked all the sensors. There was toner on the M/C unit, but after replacing the seals, the new M/C unit is clean. The customer is saying that they notice it jam more when they send a print job to it and don't notice it jamming when making copies from the glass. I have pulled the MFP board and blew out any dust and cleaned the flash rom slots. Any suggestions?
-
Last edited by Harjo; 06-17-2010, 05:51 PM. -
Sorry, no hits on my database. =^..^=If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^= -
Thanks Blackcat. I'm thinking of ordering an MFP for it after reading a tech tip about my jam problem. It's in a law office and they make a lot of straight through copies on it, so if she says it's only happening on print then I think it may be MFP time.Comment
-
I'm following your logic. Let us know how it goes. =^..^=If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
Will do. Thanks.
Comment
-
OK,
Anytime you have jam codes ending with PRI, it is mostly caused by data corruption or loss. On the MX color machines, its almost always solved by updating the print driver version, wether the original driver version seems to be working fine or not. Haven't yet had it on a Dragon, but the same principle applies. You even said it yourself.... it happens mostly on print jobs. It generally doesn't have anyting to do with the MFP board, mostly a driver corruption or problem with the spooler within windows (which is always fixed by updating/reloading the drivers fresh). Its actually quite common here. I carry all drivers on my USB stick, so I can quickly update drivers on servers whenever I see PRI jams in the jam log. It usually never comes back.
If its not the drivers... I'd be very surprised.
As it has been explained to me..... the machine feeds paper to the PPD sensors, but hasn't finished processing the print job and the machine stalls as it is waiting. Its not an actual JAM code, caused by paper being stuck on something, its more of a data loss that should be processed & written on the drum, but the paper stops & waits... then times-out, then gives a PRI jam code.Comment
-
Thanks wazza. I learned something today.
It's a good day. =^..^=If you'd like a serious answer to your request:
1) demonstrate that you've read the manual
2) demonstrate that you made some attempt to fix it.
3) if you're going to ask about jams include the jam code.
4) if you're going to ask about an error code include the error code.
5) You are the person onsite. Only you can make observations.
blackcat: Master Of The Obvious =^..^=Comment
-
Even if you learn just one thing each day, you'll never be good enough I have found....... oh well.
Definitely _PRI jams on any new Sharp is going to be driver/windows spooler related in some way. Its hardly ever the MFP, but could be......
Always perform a full driver update/reload first before any MFP changeover.Comment
-
Thanks a lot wazza. I took your advice and went to the customer and re-installed the driver with the latest and greatest from Sharp. They started using it again while I was there and everything seemed to be working correctly. I will be checking back with them on Monday to see if everything is still going ok. Thanks again and have a good weekend.Comment
-
Sweet as mate!
I'm happy that it's now working OK for you. Its a good tip to remember if you work on alot of Sharp's. _PRI jams are a PRInting issue, usually caused by the driver. If it does come back, look into the MFP.
Have a good weekend?? No I will not be having a good weekend mate.... I'm moving house..... and not looking forward to it at all!Comment
-
wow great to knowComment
-
Just following the thread. I did not know about this type of jam code and the problems with the print driver.
Thank you for the info!I thought I was getting wiser as time went on... I now realize I am just getting older.Comment
-
The jam code definitely exists, its the in service manual. I'm very surprised you guys haven't had this issue before, or you might have just not seen that particular jam code in the jam log.
It is usually a driver issue, but I have had a few cases where this code would appear, machine would stop/jam only from one particular computer, printing one particular file. On each occasion, printing this 'problem' file to any other printer in the building would work perfectly fine. On running the latest firmware in the engine & latest drivers on the server still wouldn't solve the problem, printing it from my laptop with a crossover cable worked fine, so it can be ruled out that sometimes a PC causes this issue as well. I've always known it has something to do with the windows spooler not fully processing the print job correctly or fully.
Keep an eye out for this jam code. Update the drivers if you see it.Comment
-
I have seen this code first hand on a 620 made in september of '05. This jam also happened in conjunction with an E7-06 trouble code. The solution was to thoroughly clean the drum holder(process unit), replace all the seals including the little grey sponge ones that rip. Replace the main charge and grid and clean the corona unit. Replace the drum if it's got any wear spots thru to the metal. If high voltage areas are dirty there will be electrical 'noise' and errant trouble codes for sure. Good luck.Comment
-
Just been to a call on an MX2300N for TA maintenance. Happened to notice at least 10 of these PPD_PRI jam codes recorded in the jam log. Client said it jams alot when printing one of her Microsoft Publisher documents, but everything else is fine. Found the driver version was quite old. Obviously took care of the TA Maintenance, then updated the drivers on her computers (small, 3 PC network, no server). Tested the problem Publisher document OK.
This _PRI issue is common here. Its usually a driver upgrade or firmware upgrade fix.Comment
Comment