Ticket Options

Question Profile

Question Details

TICKET ARCHIVE -> Printing to IP printer with Fiery rip

acepress - Jul 17, 2008 - 11:49 am

I am trying to print from Mac powerbook G4 with Mac OSX 10.4.11 to the fiery rip...
using ppd FieryX3E 65 BW-M server eu
over a wireless network (yes, I checked the IP address)
getting either "printer busy, will retry in 10 seconds"
or more frequently "fierycups filter error" system11 or something with an "11"
HELP!!

gsahli - Jul 17, 2008 - 12:42 pm

I'm focusing on the printer busy error first -
This is nearly Always because of incomplete setup in OS X Print & Fax prefs/Printer Setup. And usually because you didn't enter a queue name in addition to the IP address. The LPD and IPP protocols require a queue name (also called port name) to distinguish among the many printers that "could be" at one server with one IP address.
I think I found X3E online...
Typical queue names are "printer" or "print."

acepress - Jul 17, 2008 - 1:05 pm

NO MORE "BUSY" ERROR....I ENTERED A QUEUE NAME AND NOW MY JOB CONNECTS TO PRINTER, BUT DOES NOT PRINT

gsahli - Jul 17, 2008 - 4:17 pm

Try generic (postscript) driver instead of the Fiery PPD.
What do you get?

acepress - Jul 17, 2008 - 4:26 pm

got error message 'the process fierycupsfilter stopped unexpectedly with status 2"

gsahli - Jul 17, 2008 - 9:32 pm

OK, I can't help with that error - but I don't think you did what I asked, because fierycupsfilter wouldn't be called with the generic postscript driver.
I think you need to ask Fiery for help.
Sorry.

acepress - Jul 18, 2008 - 8:30 am

I chose "generic imagesetter" and thought that would be the same thing, as I had no optiion to choose"generic postscript" does that help? I am copying some of the error log to see if you can trace the problem...hope I can copy it here:
I [17/Jul/2008:16:24:41 -0400] Started filter /usr/libexec/cups/filter/fierycupsfilter (PID 693) for job 582.
I [17/Jul/2008:16:24:41 -0400] Started backend /usr/libexec/cups/backend/ipp (PID 694) for job 582.
E [17/Jul/2008:16:24:41 -0400] PID 693 stopped with status 2!
I [17/Jul/2008:16:24:41 -0400] Hint: Try setting the LogLevel to "debug" to find out more.
E [17/Jul/2008:16:24:41 -0400] [Job 582] Destination printer does not exist!
E [17/Jul/2008:16:24:41 -0400] PID 694 stopped with status 1!
I [17/Jul/2008:16:24:41 -0400] Hint: Try setting the LogLevel to "debug" to find out more.
I [17/Jul/2008:16:24:41 -0400] Saving printers.conf...
I [17/Jul/2008:16:25:49 -0400] Saving printers.conf...
I [17/Jul/2008:16:25:49 -0400] Printer '_192_168_1_51' started by ''.
I [17/Jul/2008:16:25:49 -0400] Started filter /usr/libexec/cups/filter/fierycupsfilter (PID 698) for job 582.
I [17/Jul/2008:16:25:49 -0400] Started backend /usr/libexec/cups/backend/ipp (PID 699) for job 582.
E [17/Jul/2008:16:25:49 -0400] PID 698 stopped with status 2!
I [17/Jul/2008:16:25:49 -0400] Hint: Try setting the LogLevel to "debug" to find out more.
E [17/Jul/2008:16:25:49 -0400] PID 699 stopped with status 1!
I [17/Jul/2008:16:25:49 -0400] Hint: Try setting the LogLevel to "debug" to find out more.

gsahli - Jul 18, 2008 - 10:29 am

OK, the generic I intended you to use is at the very top of the entire list - before the brand names list.
What we are trying to determine is if basic postscript will print - and that will mean that I am correct, that there is a problem with the Fiery driver.

acepress - Jul 18, 2008 - 10:38 am

I am out of the office until monday, but Mon am I will try that one...I DO suspect the fiery driver, as they have a cupsfilter fix for INTEL macs, but not earlier processors...I thought there may be a "get-around" though....If you respond to this, then I can reply to you monday am...I appreciate your efforts....

gsahli - Jul 18, 2008 - 3:27 pm

Don't be surprised if this web site tries to "complete" your question - it does that automatically. But just posting to it again reopens it.

acepress - Jul 18, 2008 - 5:52 pm

Did you get all of the error log I sent? I will be back in the office TUESDAY...I got my days confused...

gsahli - Jul 18, 2008 - 7:01 pm

Yes, I read the error log. Selecting the generic postscript driver will Not call on the fiery cups filter, and will give us confirmation that the Fiery PPD and plugins are the problem here.
Another thing from the error log - you added the printer using IPP (internet printing protocol, not IP printing). I didn't see that in the online stuff I read - LPD is the supported protocol I remember reading.
I can't fix the Fiery software, but I can help you troubleshoot to the point of being sure of what the problem is. I think it is quite possible that you are correct that there is a PPC versus intel Mac difference here. But please follow my lead first.