Xitron Plugin For Trendsetter
Xitron Plugin For Trendsetter
Trendsetter
Version 6.4.0.0
October 23, 2006
Raster Blaster
Plug-ins used by Xitron’s Raster Blaster have the same
functionality as those for the Navigator RIP and the same
options are available for configuration. Therefore, unless
otherwise specified, the information in this manual will apply
to both products. See the Raster Blaster Reference Manual for
specific configuration information.
Installation
Begin by installing the Xitron software and the Trendsetter
plug-in as instructed in the Software Installation Manual. After
installing the software, it will be necessary to complete some
preparatory steps in the Windows operating system before
configuring the Trendsetter plug-in, or attempting output to
the Trendsetter.
Do not attach the SCSI and serial (RS 232) cables until both the
Trendsetter and RIP PC are properly switched off. Attach the
serial cable to the COM port on the computer (as described on
page 11 of this document) and the SCSI cable to the SCSI card.
Complete the same connections on the Trendsetter, being sure
to fasten them tightly. Start the Trendsetter first, let it run
through its diagnostic routine and then start the PC.
Figure 2
Figure 3
Figure 4
The designations (left, top, right and bottom) represent how the RIP and
Raster Blaster “view” the plate. They also correspond directly to the “TOP”
shown in Figure 3.
From within the plug-in, use the “Center on Media Width” and
“Center on Media Length” check boxes. Additional position
Figure 5
TrendsetterMon
The Trendsetter Monitor utility – or TrendsetterMon - is a
direct communications link to the Trendsetter. In many cases,
it will be possible to run the device with only the
TrendsetterMon window visible. The RIP or Raster Blaster
window can be minimized and instructions in the
TrendsetterMon window will tell the operator what to do
next.
Figure 6
Figure 7
Figure 8
In the example above, the Trendsetter plug-in will properly send image size
data to the autoloader. When output is enabled the image size for the
second bitmap in the queue will be sent while the first bitmap in the queue
is sent to the platesetter. This will allow the system to pre-load the next
plate.
Figure 9
In this example, the plug-in will not provide the autoloader with
information about the second bitmap because none exist. Therefore, if a
second image arrives in the Active Queue after the first bitmap has imaged,
the Autoloader cannot pre-load a plate.
Figure 10
In this example the bitmap “trout-wr.ps(Y)” has been moved up and placed
in the second position of the Active Queue. The autoloader has already pre-
loaded the plate for “Xitron_Seybold Trap Test.qxd(M).” When the system
is imaging that plate, it will simultaneously pre-load the proper plate for
“trout-wr.ps(Y)” and no errors will occur.