DocuColor 252 and Fiery crashing

[fiery]

---

@Johnathan_Minton wrote:

Started from scratch with a newly saved version of the PDF file. Imposed & set-up all the settings the same way as before and have now gotten them to print and without crashing the Command Workstation software or the DocuColor 252.

Only issue with them is the "imposition" does not seem to be as tight. We were getting great bleeds past the crops but now it looks the like the file is pushed to the very most outside edges of the printer's capapbility. The crop has less than 1/32 before fading to white. Any suggestiuons?

---

 I would recommend checking out the EFI forum for any imposition questions.

http://fieryforums.efi.com/index.php

[Johnathan_Minton]

Started from scratch with a newly saved version of the PDF file. Imposed & set-up all the settings the same way as before and have now gotten them to print and without crashing the Command Workstation software or the DocuColor 252.

Only issue with them is the "imposition" does not seem to be as tight. We were getting great bleeds past the crops but now it looks the like the file is pushed to the very most outside edges of the printer's capapbility. The crop has less than 1/32 before fading to white. Any suggestiuons?

[Johnathan_Minton]

ALSO had a new hard drive installed on the Fiery (2nd reason for software install). And yes the Fiery is bustled.

[Johnathan_Minton]

Fiery software has been re-loaded twice along with the updates. One thing I noticed late in the day was that the time and date were off. I went ahead and corrected that on the Fiery but I'm not a hundred perecent sure if that is what keeps causing this issue. Let me get a new file from our designer and see what happens. 

[fiery]

Im assuming you have a bustled Fiery. 127-211 I believe just means the Fiery isnt up yet and not communicating with the machine. It sounds like the job is making the Fiery crash. You cant log in until the Fiery is rebooted and prints out a start up page. Does it only happen with that file? Is it too big or is it corrupt? Maybe have the techs reload Fiery software and put all the patches on (I believe there are 5). Also make sure you are using CWS 5 or higher.

[Johnathan_Minton]

Hi,

We have been having problems with our Fiery Software crashing and our DocuColor 252 giving a 127-211 fault code. Have been on the phone with a 2nd level analyst and our local analyst has sent our service rep out two or three times.

Basic chain of events:

PDF file is imported into Command Workstation.

All job properties are then set (paper/manual duplex) and then it gets imposed.

Once the job is released for a "process and hold" it will start to RIP and then Command Workstation crashes (we are kicked out/signed off). Printer displays nothing.

If we close out Command Workstation or even if we re-lob back-in a few seconds later the printer faults with a "127-211" fault code.

Both the printer & Command Workstation then have to be restarted.

I've got another phone call out to the 2nd level analyst now but wanted to see if anybody else has had this issue as well.

Thanks.