46
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
351
All necessary information to make the Linkfile usable in these differ-
ent environments will be included using various comments. The
most obvious ones are describing the original job size, the colors
that have been used (process and spot), the path to the ripped
page,... Double clicking the Make Link activity will open the Assem-
ble EPS Link File activity window.
9.27.1 Include Proof image
Checking this box will result in an image being included in the link
file which could be useful for later imposition or proofing purposes.
This option should be checked when proofing to a non-Nexus Rip,
where the high res information is not accessible. Unless a proof im-
age is included, the output on such a RIP will simply show a gray
box, mentioning the filename path. The Proofer Rip will be able to
use the included proof image. If unchecked, the proof image op-
tions will be disabled and the resulting link file size will be very small,
since normally only a pict preview will be included.
9.27.2 proofer device
When creating an EPS link including a Proof image, this Proof image
can be fine-tuned to the specific proofer that will be used, by select-
ing it device in the popup dialog. By selecting a proofer, its resolu-
tions will be available in the popup.
9.27.3 Link to
This popup allows you to select which file type to reference to. The
most commonly used formats are PSTI, OPPO and Separated TIFF
which refer to Raster, Vector and Screened page.
A composite Page workflow can be build by using Composite TIFF
as the file type to link to. From a composite TIFF proof, a link file will
be derived in this case
9.27.4 Proof Resolution
This setting defines the quality of the included proof image and
would typically be relatively low. It is the resolution of the proof im-
age in dots per inch. 300 dpi would be a typical setting. The result-
ing linkfile will of course be larger, depending on this resolution
value. Also printing the final PostScript from a job built with these
link files will be significantly slower when containing large proof im-
ages.
9.27.5 Compression
This defines how the image data in the proof is to be compressed.
Flate offers the most efficient compression, but some Proofer RIPs
may not yet accept it. Packbits is the default and most widely used
compression type. CCITT Group 4 compression is only applicable
to 1bit or screened proofs.
28
352
9.27.6 Preview Type
To facilitate the placement of link files in applications, a preview can
be added. The type of preview may be selected from the popup,
and is related to the application or platform in which the link file has
to be viewed. Specifying None will not include a preview at all, re-
sulting in a very small link file.
9.27.7 Advanced options
This button opens the same Advanced Options dialog as in the As-
sembler. See • Advanced options on page 310.
9.28. Make PDF Link
Where an EPS Link file is the default for Page workflows, PDF link
files may be generated as well to be used in imposition and S&R ap-
plications that support the positioning of PDF files. The PDF file will
contain an “AWSInfo” color list, containing all used separations,.
This info can be used for Step and Repeat in ArtPro.
Note that Pageboxes are stored in the PDF link file when defined in
the original PS or PDF file.
The different settings in the Make PDF Link file activity are identical
to the settings for EPS link files, explained earlier.
9.29. Make EPS Link to TIFF
This activity is a special version of the Make Link activity and is used
to make link files that reference separated TIFFs. This is typical for
a Screened Page workflow. Since there is a separate file for each
separation, this link file will have to reference multiple files, instead
of one composite OPPO or PSTI file.
The Make EPS Link to TIFF window is identical to the make link win-
dow, but separated TIFF will be the default option to link to.
42
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
353
9.30. Agfa FTP
One of the options to drive Agfa devices is to send the separated
screened data to the Agfa Printdrive over FTP. In order to be able
to accept Nexus TIFF files, the PrintDrive Open Connect option
must be enabled on the PrintDrive dongle and the Printdrive soft-
ware must be at least version 2.1. Of course on the PrintDrive hard-
ware, an FTP server must be running, and a folder shared for FTP
usage. Under these conditions a JDF workflow to the PrintDrive
may be set up from Nexus.
The job description file (JDF) specifies information needed by a
PrintDrive system to create a PrintDrive compatible job on its job list.
It is a token file, generated through the FTPExposer when output-
ting to Agfa by FTP. This mechanism allows Nexus to pass informa-
tion to the PrintDrive, which is not contained in the TIFF header tags.
Information definable in the JDF files is: job name, path names,
number of pages and separations, etc.
In the case of Agfa FTP, all separated files for a job will first be cre-
ated, before being transferred to the Agfa PrintDrive together with a
JDF file. On the PrintDrive it is important to receive all the data to-
gether, so that each job can be treated as an entity. This facilitates
further plate management and eventual proofing from the Print-
Drive.
Because of this reason, there is a default order dependency be-
tween the separation and the FTP activity, so that transferring the
data only begins upon finishing all separations.
Note:
If you send screened TIFFs over an APIS connection to PrintDrive,
every separation will be seen as a separate job.
9.30.1 Address
The IP address of the PrintDrive system (FTP server).
9.30.2 User & Password
The username and password are to be found in the NT user man-
ager console on the PrintDrive.
9.30.3 TIFF path
Defines the folder where to copy the TIFF files to. If left empty then
all TIFF files will be sent to the root FTP directory.
9.30.4 Target path
Is what will be inserted in the JDF file as path name.
42
354
9.30.5 Token path
Is the location where the JDF file must be sent to. If the Token path
is left empty then the JDF will be sent to the root FTP directory. If
you plan to use a Token path then this must be a path relative to the
TIFF path. When using more than one workflow on the PrintDrive
(e.g. for different plate sizes) it is necessary to use different TIFF and
Token paths.
9.30.6 Include Unique ID
This option includes a unique ID in the JDF. When this option is off,
every incoming ticket at the Agfa is handled as a new job, even if it
is a retry of an existing job. If the Agfa FTP activity is retried while
this option is on, the same ID will be kept, and the job will be over-
written.
9.30.7 Flats Mode
The Flats Mode enables sending to an Agfa Flat-Based workflow. If
set to “on”, “flats” will be sent over to the Printdriver as 1 single file
instead of multiple files. To send flats as multiple files, the option
should be unchecked.
9.30.8 Token File name
If a PostScript file coming from Preps contains Surface and Side in-
formation, this information will be added to the Agfa JDF. The Token
File Name can be defined using the File Naming Template.
9.31. Gerber FTP
After generating the separations in the assembler for Gerber output,
the screened TIFF files have to be transferred to the ImageHub us-
ing FTP transfer. All Gerber output devices are platesetters, and the
Image Hub takes care of the plate management, and the physical
connection with the different Gerber types. Together with the
screened TIFF files, a token file will be sent to the Image Hub, con-
taining various image positioning, exposure and media parameters.
9.31.1 Address
IP address of the Image Hub, to send the TIFF and token files to.
9.31.2 User & Password
These will be used when making the connection over FTP. Of
course this user must be defined on the Image Hub
9.31.3 TIFF & Token path
These two directory paths define where the screened TIFFs and the
token files have to be copied to.
9.31.4 Imager
The appropriate type of Gerber device has to be selected from the
popup, important for max plate sizes and available resolutions
42
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
355
9.31.5 Offset X&Y
Used to specify an offset, using the units as defined in the prefer-
ences, for the image to be positioned on the plate. By defining an X
& Y value this may be done in both directions.
9.31.6 Copies
Has to be set to more then one if multiple plates are required with
the same imaging parameters and data.
9.31.7 Media Length, Width,
...
These parameters define all plate specific characteristics. Type in
the exact plate sizes. Select the appropriate plate type from the
popup as shown. Also select whether the plate is a positive or neg-
ative plate and finally specify the thickness of the plate, which is im-
portant for the media handling and cassette selection if available.
9.31.8 Exposure
Identical to Agfa devices, the laser intensity may be adjusted from
the front end, which may be useful for linear calibration.
9.31.9 Polarity & mirror
Polarity allows you to select the imaging polarity. Selecting negative
will invert the existing TIFF image. If negative was defined through
the assembler, the image will turn positive again. The reading may
be controlled by means of the mirror check box.
9.31.10 Paper interleaved
Check this option when using paper interleaved plates.
9.32. Optronics FTP
When outputting to Optronics Imagesetters, the FTP copy proce-
dure is used to transfer screened TIFF data to the server. This ac-
tivity is almost identical to the generic FTP activity, but has an
additional token path and target path. The target is the path includ-
ed in the token to the TIFF data. This activity has no additional de-
vice specific parameters.
9.33. Saturn FTP
When driving Crosfield or Fuji RiPs through the Saturn Rip, a
screened TIFF file, together with a token file is sent to the Saturn us-
ing FTP copy. The Saturn Rip, running on a Sun Sparc station
needs the Import Option, capable of taking in 1bit screened files.
Newer imagesetters will have the Celebra Rip as front end, which is
able to read the TIFF and token file from this Nexus activity as well.
36
356
The token file contains the necessary information to ensure that the
correct resolution is selected and the correct color information for
the separations is reported.
9.34. Purup FTP
If Purup has been selected as the output device, screened TIFF files
are sent to the Purup Print server. This server may be a PC, using
the Purup Direct TIFF Exposure software and being configured as a
standalone 1 bit TIFF spooler to Purup, using a TAXI interface card.
Other possibilities are a full Purup Rip with this extension, or a Har-
lequin Rip with a Purup interface.
The FTP to Purup editor contains the standard FTP settings. There
is no separate directory path for the TIFF files and token files.
9.34.1 Media
One of the parameters included in the token file is the type of media
used. The number in the popup is linked to a specific cassette on
the imager.
9.34.2 Punch
This setting allows you to specify a predefined punch position
9.34.3 Offset
It is possible to specify that the image must be offset by the defined
amount in inches in the fast scan direction, and relative to the
punch.
9.35. Output PostScript via Appletalk
This activity is used to send a PostScript file to an Appletalk device.
In a typical NexusRIP workflow, this activity will be preceded by a
separated or composite proof activity and a convert EPS to PS ac-
tivity.
9.35.1 Printer name
In this field, the name of the Appletalk device must be entered. To
locate this device, it must be published on the network. Pressing
the Choose button will open the Chooser, which allows you to se-
lect the required printer.
9.35.2 Zone
In the chooser, the different zones will be shown on the left side. If
no different zones have been defined, an asterisk will be shown. (*)
46
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
357
9.36. Make RTL
For certain wide imposition proofers such as the HP1055 and the
Agfa Sherpa, it is recommended to drive them directly using the
RTL code rather than using conventional PostScript proofing for op-
timal performance. Many of these proofers have no built-in Post-
Script Rip, and may only be driven by RTL data.
The Make RTL activity will typically be part of a workflow where the
RTL data will not be sent directly to a proofer over FTP, but rather
copied to a predefined destination, using a file copy activity. This
activity takes in process color TIFF files generated by the Make
TIFFs for RTL activity at the required resolution, and converts them
into RTL code (e.g. J63P001.rtl), before copying.
9.36.1 Paper settings
All paper settings work the same as described in Output Epson
Proof (see earlier)
9.36.2 Enable UCR
This option is only available for Sherpa, Sherpa 2/Sherpa 43, Iris43
and Grand Sherpa output.
UCR or Under Color Removal is a printer feature and is not done by
NexusRIP. The Sherpa can do UCR on its own and it has no param-
eters. It works on a pixel level. If at a particular pixel all CMY colors
are to be printed then this option will print K instead.
9.36.3 Edit Cyan, Magenta,
Yellow, Black
Color calibration for RTL proofing devices is normally controlled us-
ing calibration files at the time of generating the process TIFF files.
In addition it is possible to adjust the color rendition values on the
proof by changing the intensity of the different inks. Each 100% of
a process ink may be mapped to a reduced amount of that ink us-
ing the edit separation buttons. In order to cut back the intensity of
the cyan on the proof for example, we press the Edit Cyan button
to open the select color window. This is the exact same window as
is used to define the process color values for undefined spot colors
in the merger. However in this case, it is only used for the process
colors. Reducing the intensity of the cyan is achieved by using the
slider, or typing in the desired value and confirming it with the OK
button. If a calibration file was used, the proof will show the result of
both.
If appropriate, cyan can be redefined with a small proportion of the
other available process colors to compensate for the actual ink col-
or in the proofer. This would not be possible with a normal calibra-
tion file only.
40
358
9.36.4 RTL Device
The RTL Device should be set according to the physical printer type
to be used. This may not only affect some physical capabilities such
as the maximum media width, but it may also result in different RTL
code. Each RTL Device is slightly different, e.g. the sherpa 2 is a
dual sided plotter, and the Sherpa 43 uses 6 inks to achieve a better
color quality.
9.36.5 Send as RGB
This check box can be enabled for 6-color output to, for example,
the HP5000. In that way, the 6-color separation will be done by the
HP Rip.
Selecting this option will result in a contone RGB RTL file, which will
be converted to six colors on the HP5000 itself. In the preceding
Make TIFFs for RTL activity, the bit depth should be set to 8. If Send
as RGB is not selected, a normal CMYK RTL file will be sent, and
only 4 inks will be used.
9.36.6 Output
In Nexus. the resulting RTL data will not always be downloaded to
the plotter directly, but may be transferred to a predefined directory.
Using the template editor, location and file naming can be set up.
9.37. Make RTL & Download
The Make RTL & Download process is performed using the FTPEx-
poser module, whose log reports parameters and codes being
downloaded.
As with the RTL convert activity, described earlier, process color
TIFF files from the HP Proof activity are the input, and an RTL file
will be created, and downloaded according to the defined parame-
ters. The RTL download icon is represented by the generic copy file
icon.
The Make RTL & Download parameter window is almost identical
to the Make RTL window, except for some specific download pa-
rameters to be defined in addition. The other parameters have been
explained in 9.36. Make RTL on page 357.
9.37.1 IP Address
The image data is sent to the RTL proofers over FTP as four color
separations. In order to locate the required printer on the network,
its IP Address must be specified. No username or password are re-
quired. The IP address is not necessary if a parallel connection is
specified through the Port popup.
43
Nexus 10.1 Reference Manual
Nexus RIP Activities
9
359
The IP address of a proofer has to be predefined in the workflow,
and may not be defined when printing using a PPD option. Proofing
over FTP will in theory also allow you to proof to a remote proofer
over the internet. If the proofer is not online, or there is a problem
with the IP address, an error will be generated in the FTPExposer
9.37.2 Port Type
The default setting here is HP which has support for queue man-
agement. However some older proofer types may require the LP
setting. Some plotters, lacking an ethernet interface, may require a
parallel cable connection. In the latter case, there is no need to
specify the IP address. Sending over Parallel cable is slower than
using FTP transfer over ethernet.
9.37.3 Module
The FTP Exposer module takes care of the download activity. If mul-
tiple FTP Exposers have been created, this popup can be used to
assign a specific FTP Exposer to the download activity of the work-
flow. A more detailed explanation on how to set up and use multiple
modules can be found in 2.14.3 Multiple Modules on page 86.
9.38. Expose Epson Proof
The direct driver available for Epson Stylus 7000 and 9000 series is
limited to CMYK only. The Output Epson Proof activity takes in the
CMYK TIFF files from the Make Epson Proof activity and converts
these to an EscP file, which is the Epson internal file format.
9.38.1 Paper
• Paper Width
This field, expressed in preference units should correspond to the
physical paper width in the printer. The indicated value of 914.4
mm corresponds to the common size of 36 inches for large for-
mat proofers.
• Center Width
This check box is only available if the paper width is not equal to
0. Checking this option will center the job if it is narrower than the
actual full paper width. In this case there will be a margin on either
side of the image, equivalent to half of the difference between the
image width and the paper width.
• Paper Height
There is no specific way to generate a bottom margin, but if a pa-
per height is set which is larger than the image height, a white
space area below the proof image will result. For roll fed media,
41
360
this is not very relevant, since the exact height will always be
used. This setting is primarily for output devices using sheet fed
media, where the available paper height is limited.
• Center Height
When a value has been specified for the paper height, this option
becomes available. Checking it will result in the image being cen-
tered in the vertical direction so that top and bottom margin will
be equal.
• Paper Thickness
This option allows the user to define the thickness of the media
to be used. If the feature is enabled then the edit field allows a
number in the range 0.0 mm -> 1.6 mm to be entered. The de-
fault is 0.2mm.
• Feed Adjustment
The print head prints a band of scan lines at a time. When a band
has been completed the paper is then fed so that the next band
can be printed. There can be a small deviation in the amount of
paper fed, due to the thickness (and possibly other properties) of
the media. To correct this you have to adjust the amount of feed,
dependent on the media.
If the paper feed is incorrect you can see one of two possible ef-
fects:
- Too much feed and each new band will be printed slightly too
far after the band before it. This will result in white horizontal lines
(spaces) at regular intervals in the output.
- Too little feed and each new band will slightly overprint the band
before it. This will result in dark horizontal bands at regular inter-
vals in the output.
If the feature is enabled then the edit field allows a % value in the
range -1% -> +1% to be entered. The default is 0%.
If the feature is not enabled, the setting in the printer will be used.
An option called “Define Adjustment” enables the feature.
This feature is not available for 7000/7500 or 9000/9500.
• Roll Feed
Having this option unchecked will use cut sheets and pick them
up from the standard media basket. On an Epson 9000, cut
sheets vary from A3 - B0+.
Checking this option will use the Roll paper media. Auto cut will
automatically cut the roll after each job, and Bottom margin con-
trols the margin at the end of the job to be left.
Documents you may be interested
Documents you may be interested
