ARM550n Getting the PPD_PRI Jam Code

[leo34staffs]

Re: ARM550n Getting the PPD_PRI Jam Code

I have just had this code on a hercules (mx-m1100), at first i cleaned all sensors then it worked again, but thats maybe because when i came out of sim mode it lost the print job that was causing it to fail.

I will check drivers if i get this call again.

Thanks for the info Wazza

[ZOOTECH]

Update of fix, it was the MFP pwb which was ordered under warranty; all is good so far.

[ZOOTECH]

Well, the memory in slot 5 was replaced but did not fix the NG in TC 60-1. The hotline verified that their memory test on same model was ok. MFP pwb is now on order.

Zootech... I've never seen that code appear on a copy job..... it always been on a print job here. Thats interesting, but you're on the right track with the memory I'd say.

Bill..... Man, you are too funny. I was waiting for that line all this time, seeing no-one else seemed to have this issue. Our toilets flush the opposite direction to yours, but our copiers dont work any differently.......

[bonnie750]

Wazza, the probable reason is that your machines are all upside down mate!!!!!!

Bill

[ZOOTECH]

I had a PPD_PRI code at setup on a MXM623N yesterday when copying from the glass. Test command 60-1 showed slot 5 (DIMM5) as NG and the memory chip has been ordered; I'll post if that fixes the problem. Another jam code from the doc feeder was SPSD_SCN. PPD_PRI code indicate a timing issue when "The IMAGE_PREPARE command is sent from the PCU to the ICU. and The END_IMAGE_PREPARE command is received from the ICU. (50 sec)".
The SPSD_SCN code is the "Arrival at temporal stop position. Exposure start command from ICU to SCU no reception time-out (120 sec)".
Other techs have seen the _PRI codes and have now been told of the print driver fix; thanks wazza.

Too easy mate.

I'm still surprised you guys have never seen this before. We use the same drivers here that are used up north.

(maybe the jam logs are simply cleared without taking any notice........)

[jprecht]

this prob/solution discussion is why we are on here. I'd like to also add my thanx 2 wazza 4 pointing out something thats easy to overlook!!!

I agree with the MS Publisher issues. I had a call at the end of last year, with a small school printing their end-of-year newsletter/school book. They were using Publisher, and they logged a call saying the machine just wouldn't print (Sharp MX4501N). The data light was flashing, and had been doing so for many hours. Traced the problem to the print spooler file being 9.5Gb!!! They has used Publisher to make a page with hundreds of small, very high res pictures into a collage of all the kids. I gave them the option of either waiting until it printed or change over to a different program and print from there. They opted to convert the file into a PDF. Dont know how they did it, but it definitely worked and it was a much more sensible spooling size.

As a test, they left it spooling the Publisher file overnight and it still hadn't printed the first page next morning!

[blackcat4866]

Just my 2 cents:

Microsoft Publisher (especially the older versions) seem to have many driver conflicts, and some very unexpected results. =^..^=

[Harjo]

Just wanted to post an update. Thanks again Wazza, the machine has been going strong ever since I loaded new drivers. I've let all the other techs here know what to try/do should they see that happening.

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.

[Dave]

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.

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.

[TennWalker]

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!