Tracking jobs printed from a Fiery using PaperCut

KB Home   |   Tracking jobs printed from a Fiery using PaperCut

First, what does a Fiery do?

Using a Fiery in a digital print press environment provides enhanced image and color quality along with productivity benefits. Managing production print with PaperCut allows Fiery customers to allocate cost with Fiery tracking and reporting. Administrators can now limit unnecessary printing and encourage positive user behaviour to enable Fiery cost recovery.

Unlike most printers, devices fitted with Fiery servers or controllers have the ability to hold and reprint jobs and manage the print job settings after PaperCut has analyzed the job on the print server.

How do we track jobs that are re-printed on Fierys?

As PaperCut logs print jobs at the server, rather than when the Fiery is used to modify, proof or otherwise reprint the job, a custom program is needed to integrate PaperCut to track print jobs released from Fiery servers/controllers.

PaperCut has developed an executable that checks Fiery print logs and updates PaperCut with the jobs that are reprinted. It uses APIs from both PaperCut and those similar to Command Workstation to communicate with Fiery and track those jobs.

Currently with support for Windows the program enables connection to a PaperCut server and multiple Fiery devices over the network. It checks all the Fiery job logs regularly and updates the PaperCut server with any new jobs it finds.

Download the PaperCut Fiery Program

The latest versions for the PaperCut Fiery Program can be found below:

These zip files contain a README.txt (Windows) or README.mac (Mac) file that describes how to install this program, and connect it to PaperCut and one or more Fiery command workstations.

We recommend running this executable on your PaperCut server for simplicity, although it could be run from any workstation that has network access to both the PaperCut server and any Fierys. We also recommend having a Scheduled Task on your server to start this executable in the background as a service.

Release History

  • 19th February 2019 - Updated the Windows 64bit version. Fixed an issue that caused the Fiery tool to not retrieve jobs. Also added extra logging to show raw Fiery Box replies and to log when jobs are skipped due to zero printed pages. N.B. If you need an updated version of the package for mac or 32bit windows, please contact us and quote Issues PC-12155 and PC-15261
  • 21st August 2017 - Updated the Windows program for connecting to more recent Fiery controllers which require more recent SSL protocols. Previous fiery binary would result in an error: “[errno 8] _ssl.c:504: EOF occurred in violation of protocol” N.B. If you need an updated version of the package for mac, please contact us and quote Issue PC-12155.

Support

If you’re having issues configuring the Fiery setup with PaperCut - have a look over on the Troubleshooting Fiery page for some troubleshooting tips.

Otherwise if you’re still seeing issues after that, have a chat with us!


Categories: Printers


Keywords: fiery, rips, rip, efi, Fiery Logs, Fiery cost recovery, Fiery tracking, cost allocation, production print, cost monitoring

Comments

Share your findings and experience with other PaperCut users. Feel free to add comments and suggestions about this Knowledge Base article. Please don't use this for support requests.

Article last modified on May 16, 2019, at 07:30 PM
Printable View   |   Article History   |   Edit Article