Fiery Keeps Disconnecting - Do I really need a fiery?

[TradeGraphicDesign]

Hi folks, I've just put a 'new to me' Ricoh Pro C520' in, I'm chuffed to bits with the quality. But, I've managed to get the sum total of around 6 SRA3 sheets out the machine.
The technician just came back today, the Fiery Rip keeps disconnecting, and dropping off the machine.
Command Workstation tries to process PDF's - small files, but tanks after 5 mins and drops the connection with the RIP.

I've tried just printing into the machine, but because it has the fiery, the files must end up in the processing Q

Is there anyway to ditch the fiery, and just print the files into the machine?

Would quality suffer? I'm just not looking forward to this level of downtime, especially not from the RIP.

Thanks in advance for any advice

PS - I'm on a Mac - would I be better advised to install CW on a windows machine, is that likely to improve things

All the best

Tim

 

[SoggyWinter]

Ricoh should have a Fiery helpdesk that you or the tech can access if you're under a support contract. Also try communities.fiery.com

 

[DYP]

Is the Mac CWS disconnecting from the Fiery or the Fiery disconnecting from the printer?

 

[PricelineNegotiator]

Hi folks, I've just put a 'new to me' Ricoh Pro C520' in, I'm chuffed to bits with the quality. But, I've managed to get the sum total of around 6 SRA3 sheets out the machine.
The technician just came back today, the Fiery Rip keeps disconnecting, and dropping off the machine.
Command Workstation tries to process PDF's - small files, but tanks after 5 mins and drops the connection with the RIP.

I've tried just printing into the machine, but because it has the fiery, the files must end up in the processing Q

Is there anyway to ditch the fiery, and just print the files into the machine?

Would quality suffer? I'm just not looking forward to this level of downtime, especially not from the RIP.

Thanks in advance for any advice

PS - I'm on a Mac - would I be better advised to install CW on a windows machine, is that likely to improve things

All the best

Tim

You definitely want the Fiery. You will come to appreciate it. Totally understand you not "getting" what it does just yet.

What do you mean by "tanks after 5 mins"? Does it process the same file for 5 minutes? Should only take a few seconds, maybe 15 at the max if it's a normal job.

 

[TradeGraphicDesign]

I managed to get one sheet off just now.
which it wouldn't do last night.
When I print a job into CW, it just holds in processing, and when I go 'properties' it says there is no media, 'do I want to set as unassigned' so maybe the CW isn't configured properly.
I've simplified my networking arrangement, so that's maybe why the computer and printer could actually connect to each other this morning.
But, the Fiery just seems to throw a wobbly and disconnect from the machine every 5-10 mins
I have a '00' on the back of the machine, on the red LED, and FF on startup.

The Printer is showing the attached error message too (that's a new one) - it did that about 5 mins after printing the first sheet.

 

[TradeGraphicDesign]

Ricoh should have a Fiery helpdesk that you or the tech can access if you're under a support contract. Also try communities.fiery.com

Thanks, I'm a second user so i'm not 100% where the RIP support is coming from. We've had a technician in last week, and he was here yesterday.

 

[TradeGraphicDesign]

Is the Mac CWS disconnecting from the Fiery or the Fiery disconnecting from the printer?

It seems to be the RIP disconnecting from the printer.
The Icon disappears, and then CW disconnects
Thanks in advance
Tim

 

[TradeGraphicDesign]

You definitely want the Fiery. You will come to appreciate it. Totally understand you not "getting" what it does just yet.

What do you mean by "tanks after 5 mins"? Does it process the same file for 5 minutes? Should only take a few seconds, maybe 15 at the max if it's a normal job.

I'll persevere then - Thanks for the advice.
I got 1 sheet out this morning.
Then, a strange error on the printer itself.

For some reason, when I send a PDF into the processing and hold Q, it just processes, and doesn't ever finish.
A file that I dropped into the Q last night, was available to print, which I sent into the machine, and I got a copy off.

CW doesn't have all the paper library options too. I do a little youtube hunting and see If I can figure out how to get the suite of different media types on CW.

Any suggestions, I'm very grateful for

Print quality is outstanding, so I'm keen as mustard to get this thing firing

Best regards

Tim

 

[adriansto]

Fiery is only a PC computer. So ask someone who repair PCs.
Can be not cooling good the processor, or the electric power supply or bad memory contact or bad electronic contacts on plugs and jacks.

 

[PricelineNegotiator]

For some reason, when I send a PDF into the processing and hold Q, it just processes, and doesn't ever finish.
A file that I dropped into the Q last night, was available to print, which I sent into the machine, and I got a copy off.

Something is wrong. Things do not take this long to process in modern version of the Fiery, nor a Fiery from 10 years ago. I would talk to the Fiery support team immediately and have them help you with the problem.

Fiery is only a PC computer. So ask someone who repair PCs.
Can be not cooling good the processor, or the electric power supply or bad memory contact or bad electronic contacts on plugs and jacks.

Sorry, I disagree. This sounds like a software gone bad issue. Perhaps bad settings or a bad PDF, or a corrupted installation of the Fiery software.

 

[gregbatch]

DISCONNECTING: Is the Fiery plugged into a power backup or power filter? Unstable power can cause frequent disconnects.
STALLING: Do you have the PDF print engine checkbox? If so, make sure it is checked. If not, ask the tech if it is available to activate. I had it on one Fiery and had to activate it on another. I've had many PDFs that would not print without that checked. I've also had files that wouldn't print with that on. I replaced all the fonts to see if it would print, and it did. So I replaced one-by-one to see which font was causing the issue. I reinstalled that font and had no more issues. Another font related check: make sure fonts are being embedded in the PDF. If "only use local fonts" is checked, you will almost always have problems.

 

[TJPrinter]

I have a '00' on the back of the machine, on the red LED, and FF on startup.

The Printer is showing the attached error message too (that's a new one) - it did that about 5 mins after printing the first sheet.

This is what Fiery says about the 00 and FF.

FF shown on the 7-Segment LEDs after the embedded Fiery controller becomes Idle or shortly at the startup does not indicate an error status. When FF is displayed during normal operation, it is similar to 00 as seen on previous models of embedded Fiery Controllers.

However - If during the startup,the Fiery Controller hangs displaying FF and never boots to idle, this could indicate a hardware problem.

In this instance, the cause of the failure could be due to one of the following;

• Faulty motherboard
• Faulty or missing CPU

Suggested Action;

1. Replace the motherboard.

If problem persists -

1. Replace the CPU.

You may want to check the cable that connects the Fiery to the engine, it could be that you have a bad connection that's causing the Fiery to lose communication with the engine.

 

[tngcas]

Have you tried printing a different pdf file? Every now and then we get a bad pdf file that will crash the fiery every time we try to process it.
It's super annoying until you figure out it's a corrupted pdf file.

 

[jwheeler]

Assuming you mean the C5200, since that is an older unit launched in 2017, my first guess would be the version of Command Workstation you installed could be causing a conflict. When you do a new install of CWS, it automatically does the latest version unless you force it to install an older one. Alternatively, you may have let the server do some updates when you first plugged it in and those newer updates can sometimes cause issues for the older Fierys. A Fiery specialist should be able to revert you back to an older version if that's the case.

I also have a different opinion from others in that you don't "Need" the Fiery, however, it is an industry standard that has an excellent workflow and color control. If you decided you wanted to just use the Ricoh controller, you would need to purchase one and have it installed/converted from the Fiery controller.

 

[TJPrinter]

It’s a good idea to make sure you’re running compatible software and operating system as jwheeler pointed out. You can find all that information here from Fiery. You'll find that on the same page you can download older versions of CWS. The rip you have would be running on Linux and it shouldn’t make any difference if you’re CWS is on a Mac or a PC. You can check to see if AppleTalk is enabled by going to your network tab while in the configuration settings (CWS, Server > Configure > Network) also go to Job Submission and turn off Windows printing, if enabled. My guess would be that this is already setup correctly since you're able to send files and you're connected to the RIP, at least temporarily. I always select “Print Start Page” under Fiery Server in same configuration settings area. I shut everything down at the end of the day and like to know that the RIP is running and connected to the engine the next morning, and the start up page lets me know I’m ready to go.

I realize that this a used machine, but the install is still new. If you’re under a service contract your provider should have made sure everything was running smoothly before they left the installation. Your service provider will need to be your go between for you and Fiery. The only help you'll ever get from Fiery is on their website or forum.

 

[bcr]

Assuming you mean the C5200, since that is an older unit launched in 2017, my first guess would be the version of Command Workstation you installed could be causing a conflict. When you do a new install of CWS, it automatically does the latest version unless you force it to install an older one. Alternatively, you may have let the server do some updates when you first plugged it in and those newer updates can sometimes cause issues for the older Fierys. A Fiery specialist should be able to revert you back to an older version if that's the case.

I also have a different opinion from others in that you don't "Need" the Fiery, however, it is an industry standard that has an excellent workflow and color control. If you decided you wanted to just use the Ricoh controller, you would need to purchase one and have it installed/converted from the Fiery controller.

I have a c5310 which is the newer version of the machine but it has built into it a Ricoh controller as well as the external fiery which I specced.

I am able to use both the Ricoh controller and the fiery controller alongside each other without needing to change anything in between using them. In my experience - many Ricoh production techs do not even realise this is installed or possible. They looked utterly bewildered when I explained we use both as they did not know it could be done.

I don't know if this is also the case for the c5200 but it is worth trying. Ricoh support has drivers for the c5200 - so maybe check and see if you can search for the printer and install using those drivers.

Re. the fiery - is this an external controller which you can plug a keyboard mouse and monitor into, or is it a bustled one fitted on the back of the printer?

If it's the former - have you tried printing from that instead of your Mac? If so - problem is likely with your Mac.

Will the fiery interface on the machine print test pages, calibration pages, configuration pages etc?

Separately, try installing CWS (perhaps an older version) onto a PC - and not one running windows 11, to see if you can get it working that way.

Windows 11 has caused all manner of issues with fiery drivers etc. I don't know if that extends to CWS as well, but this is a process of elimination. First thing I would do is try printing straight from the controller (if it's external), and otherwise from a windows (10) machine.

 

[TradeGraphicDesign]

A little update on the kit, all is good, no more disconnecting, although, I can't help but whince a little as I type this It was just some network issues, with my slightly overcomplicated setup here. The fiery has been really stable, and I'm chuffed to bits with the kit so far.

Thanks for everyone's suggestions, really appreciated. Tim