Setting up RIP devices

KB Home   |   Setting up RIP devices

Main.RIPDevices History

Hide minor edits - Show changes to output

Changed lines 3-16 from:
Q: I have a RIP device.  How can I use PaperCut to track printing via the RIP?

The key is to set up the RIP between the server running PaperCut and the physical printer.  The job will move from the workstation to the server (running PaperCut) via the server's shared queues.  The server then directs the job to the RIP which in turn directs the job to the physical printer.

->'''Workstation''' → '''Print Server''' → '''RIP''' → '''Printer'''

Setting up a RIP device for use with PaperCut generally involves the following steps:

# On the server where PaperCut is installed, set up a printer/RIP driver and configure it to point the RIP.  Test printing directly on the server first before continuing to the next step.
# Share this print queue so that workstations on the network can access it
# Configure all workstations to print to the share (and not directly to the RIP)

PaperCut can then audit and control access to the print queue(s).  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.  Note that any job manipulation carried out on the RIP (cancellation, duplication, partial printing) will not be reflected in PaperCut as the job has already been tracked and charged.

to:
Added lines 22-35:
Q: I have a RIP device.  How can I use PaperCut to track printing via the RIP?

The key is to set up the RIP between the server running PaperCut and the physical printer.  The job will move from the workstation to the server (running PaperCut) via the server's shared queues.  The server then directs the job to the RIP which in turn directs the job to the physical printer.

->'''Workstation''' → '''Print Server''' → '''RIP''' → '''Printer'''

Setting up a RIP device for use with PaperCut generally involves the following steps:

# On the server where PaperCut is installed, set up a printer/RIP driver and configure it to point the RIP.  Test printing directly on the server first before continuing to the next step.
# Share this print queue so that workstations on the network can access it
# Configure all workstations to print to the share (and not directly to the RIP)

PaperCut can then audit and control access to the print queue(s).  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.  Note that any job manipulation carried out on the RIP (cancellation, duplication, partial printing) will not be reflected in PaperCut as the job has already been tracked and charged.

Changed lines 19-26 from:
A: Some `RIPs have the ability to re-send, proof, or edit jobs directly on the RIP.  These jobs, because they don't pass via the server will not be tracked by PaperCut.  Sites conducting this type of proof -> print procedure in a RIP environment may like to consider using the [[https://www.papercut.com/products/ng/manual/ch-shared-accounts-popups.html#ch-shared-accounts-popups-manager|manager mode popup]] to manually allocate costs.  The manager mode popup will trigger/display when the proof is printed to the PC.  The popup can then be filled in to assign extra costs/functions that will be applied at the RIP layer such as:
to:
A: Some `RIPs have the ability to re-send, proof, or edit jobs directly on the RIP.  These jobs, because they don't pass via the server will not be tracked by PaperCut.  There are two options depending on the type of RIP:

# If the device is a Fiery RIP, PaperCut has worked with EFI to develop a program to assist in integration between the two systems.  Please see [[TrackingJobsOnFiery|+]] .
# On other devices, you may need to consider manual cost allocation.  This is explained in some more detail below.


!!!Manual Allocation

  Sites conducting this type of proof -> print procedure in a RIP environment may like to consider using the [[https://www.papercut.com/products/ng/manual/ch-shared-accounts-popups.html#ch-shared-accounts-popups-manager|manager mode popup]] to manually allocate costs.  The manager mode popup will trigger/display when the proof is printed to the PC.  The popup can then be filled in to assign extra costs/functions that will be applied at the RIP layer such as:
Changed lines 33-36 from:
!! Tracking print jobs on Fiery controllers

TrackingJobsOnFiery describes how to track print jobs on Fiery controllers from PaperCut.
to:


''Also see:'' [[
TrackingJobsOnFiery|+]]
Changed lines 29-30 from:
If you wish to track jobs printed on Fiery controllers then contact [[https://www.papercut.com/support/ | support]].
to:
Changed line 28 from:
[TrackingJobsOnFiery] describes how to track print jobs on Fiery controllers from PaperCut.
to:
TrackingJobsOnFiery describes how to track print jobs on Fiery controllers from PaperCut.
Added line 28:
[TrackingJobsOnFiery] describes how to track print jobs on Fiery controllers from PaperCut.
Deleted lines 30-31:
Depending on your operating system and Fiery models they may be able to supply with a script that tracks jobs on the Fierys. All recent Fierys and PaperCut running on Windows should be supported. Other configurations may be supported.
June 14, 2013, at 06:00 AM by Peter - Note on Fiery
Changed lines 26-31 from:
to:
!! Tracking print jobs on Fiery controllers

If you wish to track jobs printed on Fiery controllers then contact [[https://www.papercut.com/support/ | support]].

Depending on your operating system and Fiery models they may be able to supply with a script that tracks jobs on the Fierys. All recent Fierys and PaperCut running on Windows should be supported. Other configurations may be supported.

Changed lines 20-26 from:
 * The copies or final number of non-proof prints
 * Color changes
 * Cover pages
 * Finishing options such as stapling, binding, etc.
 * Manual tasks such as delivery, post, etc.

to:
* The copies or final number of non-proof prints
* Color changes
* Cover pages
* Finishing options such as stapling, binding, etc.
* Manual tasks such as delivery, post, etc.

Changed line 30 from:
[-Keywords: fiery-]
to:
[-Keywords: fiery, rips, rip, efi, power press-]
Changed lines 19-20 from:
A: Some `RIPs have the ability to re-send, proof, or edit jobs directly on the RIP.  These jobs, because they don't pass via the server will not be tracked by PaperCut.  Sites conducting this type of proof -> print procedure in a RIP environment may like to consider using the [[https://www.papercut.com/products/ng/manual/ch-shared-accounts-popups.html#ch-shared-accounts-popups-manager|manager mode popup]] to manually allocate costs.
to:
A: Some `RIPs have the ability to re-send, proof, or edit jobs directly on the RIP.  These jobs, because they don't pass via the server will not be tracked by PaperCut.  Sites conducting this type of proof -> print procedure in a RIP environment may like to consider using the [[https://www.papercut.com/products/ng/manual/ch-shared-accounts-popups.html#ch-shared-accounts-popups-manager|manager mode popup]] to manually allocate costs.  The manager mode popup will trigger/display when the proof is printed to the PC.  The popup can then be filled in to assign extra costs/functions that will be applied at the RIP layer such as:
 * The copies or final number of non-proof prints
 * Color changes
 * Cover pages
 * Finishing options such as stapling, binding, etc.
 * Manual tasks such as delivery, post, etc.


Changed lines 19-20 from:
A: Some RIPs have the ability to re-send, proof, or edit jobs directly on the RIP.  These jobs, because they don't pass via the server will not be tracked by PaperCut.  Sites conducting this type of proof -> print procedure in a RIP environment may like to consider using the [[https://www.papercut.com/products/ng/manual/ch-shared-accounts-popups.html#ch-shared-accounts-popups-manager|manager mode popup]] to manually allocate costs.
to:
A: Some `RIPs have the ability to re-send, proof, or edit jobs directly on the RIP.  These jobs, because they don't pass via the server will not be tracked by PaperCut.  Sites conducting this type of proof -> print procedure in a RIP environment may like to consider using the [[https://www.papercut.com/products/ng/manual/ch-shared-accounts-popups.html#ch-shared-accounts-popups-manager|manager mode popup]] to manually allocate costs.
Added lines 17-20:
Q: Can jobs instigated by the RIP be tracked by PaperCut?

A: Some RIPs have the ability to re-send, proof, or edit jobs directly on the RIP.  These jobs, because they don't pass via the server will not be tracked by PaperCut.  Sites conducting this type of proof -> print procedure in a RIP environment may like to consider using the [[https://www.papercut.com/products/ng/manual/ch-shared-accounts-popups.html#ch-shared-accounts-popups-manager|manager mode popup]] to manually allocate costs.

Changed lines 3-8 from:
Q: I have a RIP and would like to use it on my network with PaperCut?

The key is to set up the RIP between the server running PaperCut and the physical printer.  e.g.  The job will move from the workstation to the server (running PaperCut) via the server's shared queues.  The server then directs the job through to RIP which in turn directs the job to the physical printer.

To set up a RIP device with PaperCut, use the following configuration:
to:
Q: I have a RIP device.  How can I use PaperCut to track printing via the RIP?

The key is to set up the RIP between the server running PaperCut and the physical printer.  The job will move from the workstation to the server (running PaperCut) via the server's shared queues.  The server then directs the job to the RIP which in turn directs the job to the physical printer.

->'''Workstation''' → '''Print Server''' → '''RIP''' → '''Printer'''

Setting up a RIP device for use with PaperCut generally involves the following steps
:
Changed line 12 from:
# Share this print queue (e.g. a shared print queue that workstations on the network can access)
to:
# Share this print queue so that workstations on the network can access it
Changed lines 15-16 from:
PaperCut can then audit and control access to the print queue(s).  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.
to:
PaperCut can then audit and control access to the print queue(s).  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.  Note that any job manipulation carried out on the RIP (cancellation, duplication, partial printing) will not be reflected in PaperCut as the job has already been tracked and charged.
Changed line 18 from:
''Categories:'' [[!Printers]]
to:
''Categories:'' [[Category.Printers|+]]
Changed lines 13-14 from:
PaperCut can then monitor and control access to the print queue(s).  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.
to:
PaperCut can then audit and control access to the print queue(s).  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.
Changed lines 3-4 from:
Q: I have a RIP and would like to use it on my network with PaperCut (PaperCut to monitorand control jobs)?
to:
Q: I have a RIP and would like to use it on my network with PaperCut?
Changed lines 13-14 from:
PaperCut can then monitor and control access to the print queue.  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.
to:
PaperCut can then monitor and control access to the print queue(s).  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.
Added line 8:
January 29, 2009, at 10:17 AM by 218.214.136.115 -
Added lines 3-6:
Q: I have a RIP and would like to use it on my network with PaperCut (PaperCut to monitorand control jobs)?

The key is to set up the RIP between the server running PaperCut and the physical printer.  e.g.  The job will move from the workstation to the server (running PaperCut) via the server's shared queues.  The server then directs the job through to RIP which in turn directs the job to the physical printer.

Changed lines 8-9 from:
# On the server where PaperCut is installed, set up a printer to point to the RIP
# Share this printer (e.g. a shared print
queue)
to:
# On the server where PaperCut is installed, set up a printer/RIP driver and configure it to point the RIP.  Test printing directly on the server first before continuing to the next step.
# Share this print
queue (e.g. a shared print queue that workstations on the network can access)
Changed lines 12-13 from:
PaperCut can then monitor and control access to the print queue.  The print queue forwards print jobs to the RIP device, which in turn forwards them to the printer.
to:
PaperCut can then monitor and control access to the print queue.  Once the job is spooled to the server, the job will be forwarded to the RIP device, which in turn forwards them to the physical printer.
Changed lines 4-7 from:
* Set up a print queue to point to the RIP device
* PaperCut should be installed on the system hosting this queue
* Have users
print to this queue, i.e. don't let them bypass it - enforce access control if necessary
to:
# On the server where PaperCut is installed, set up a printer to point to the RIP
# Share this printer (e.g. a shared
print queue)
# Configure all workstations to print to the share (and not directly to the RIP)

January 16, 2007, at 01:21 AM by 218.214.136.161 -
Added lines 1-13:
(:title Setting up RIP devices :)

To set up a RIP device with PaperCut, use the following configuration:
* Set up a print queue to point to the RIP device
* PaperCut should be installed on the system hosting this queue
* Have users print to this queue, i.e. don't let them bypass it - enforce access control if necessary

PaperCut can then monitor and control access to the print queue.  The print queue forwards print jobs to the RIP device, which in turn forwards them to the printer.

----
''Categories:'' [[!Printers]]
----
[-Keywords: fiery-]

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 September 15, 2014, at 11:24 PM
Printable View   |   Article History   |   Edit Article