MX4100 PPD2_PRI

[hammer]

Hi Guys, anyone seen the jam code PPD2_PRI? we get it and it causes a paper jam. It relates to an Image Prepartion Wait Timeout. I have seen a link on SharpSearch relating to this issue arising when a DSK is installed on an MX2300/2700, but we an it on an MX4100 with no DSK. Latest firmware is installed, and when it jams it cannot be tied to any particular job type. Any ideas?

[Akitu]

Re: MX4100 PPD2_PRI

On the 3501 the cause of this code was bad memory in DIMM slot 2. I'd have to assume the same for the 4101. Replace with a new 512MB DDR2 memory chip and it should resolve your issue.

(Parts guide section 43, part 19)

[divad2k1]

Re: MX4100 PPD2_PRI

Also check your primary transfert belt, had a flipped cleaning blade giving me this problem.

[bonnie750]

Re: MX4100 PPD2_PRI

I've seen this before but only when a citrix server is being used to process the print jobs. there is an update for the driver on the Sharp site

Bill

[bonnie750]

Re: MX4100 PPD2_PRI

any fix on this?

[Chr15tophe]

Re: MX4100 PPD2_PRI

PPD2_Pri jams can be caused by memory, laser or hard drives.

We had an MX-2300N do this, replaced the laser and all was ok

[hammer]

Re: MX4100 PPD2_PRI

We have switched the memory DIMMs on our machine and this seems to have worked......so far. The users are directing some prints through a citrix driver so there still may be something in the background that is causing this.

[Akitu]

Re: MX4100 PPD2_PRI

So, the PPD2_PRI jams have stopped but you still suspect the citrix server of causing some problems? Glad to see it's fixed, for now.

[hammer]

Re: MX4100 PPD2_PRI

Back in the dog-house! The memory didn't sort the problem - call came back in. We're are looking at the HDD and LSU. Dont you just love Monday's!

[Akitu]

Re: MX4100 PPD2_PRI

I'd take a look into Bonnie's suggestion then, about an updated driver for citrix servers. I deal exclusively with Windows, as our customers don't operate in mac environments or linux, so I'm unfortunately a little useless in that dept.

Shame about the memory not being the fix. Seemed promising at first.

[Akitu]

Re: MX4100 PPD2_PRI

Apparently these PPD2_PRI jams can also be caused by certain documents. One such case was a word document with multiple small images made into a collage on the first page. Upon further inspection, the small images were all taken with a 10megapixel camera and had a massive file size. The machine just would not rip the page.

Looking at the job log data from the machine, you should be able to figure out if it's one user or all who are causing this. Check it out and see what you find.

Another possibility would be to save the document as a .prn file and try printing directly from a USB drive, because the processing is done at the pc end, saving it as an image, instead of a spooled file into the machine's memory.

[hammer]

Re: MX4100 PPD2_PRI

Hi All, we are still having issues with this one. So far we have;

1. Replaced the Hard Drive
2. The Print Control Board
3. The Memory
4. PCU PWB
5. Transport assembly
6. Firmware is updated
7. The customer has also installed citrix drivers

The customer has now said that the issue is occuring when copying????? I will grab a job log from it, but does anyone have any ideas?

[ZOOTECH]

Re: MX4100 PPD2_PRI

Hi All, we are still having issues with this one. So far we have;

1. Replaced the Hard Drive
2. The Print Control Board
3. The Memory
4. PCU PWB
5. Transport assembly
6. Firmware is updated
7. The customer has also installed citrix drivers

The customer has now said that the issue is occuring when copying????? I will grab a job log from it, but does anyone have any ideas?

Hope this link works and will help you.
http://www.copytechnet.com/forums/sh...-jam-code.html

[DINGO]

Re: MX4100 PPD2_PRI

Hope this link works and will help you.
http://www.copytechnet.com/forums/sh...-jam-code.html

Hi friend
the link isn t more avaiable?
thank you

[ZOOTECH]

Re: MX4100 PPD2_PRI

Hi friend
the link isn t more avaiable?
thank you

http://www.copytechnet.com/forums/sh...hlight=arm550n

Try this one DINGO, I think older links may have been corrupted when the hacker attacked.
Thanks to our friend OMD-227.