Managing your Task Processors
This section explains how you can manage your Task Processors from the System Overview window. You can start, stop and restart any Task Processor. Stopping a Task Processor (if you are not planning to use it) will improve system performance, since Asanti will then require fewer system resources. Output Task Processors need to be restarted if you change the configuration of the associated output device.
Additionally, Task Processors associated with physical output devices can be put online and offline. You can also create a PostScript Printer Description file (PPD) containing all job-related information specific for your output environment.
TIP: In Asanti, you can create PPD files for different PS Printer Drivers for Macintosh as well as PC. You can further specify some content-related options.
See also “Monitoring your Task Processors”.
To start a Task Processor
1 In the System Overview, locate the inactive Task Processor.
When a Task Processor is inactive, the icon will have static horizontal stripes running through it.
 |
2 Context-click the Task Processor, and select Start from the context menu.
To stop a Task Processor
1 In the System Overview, locate the active Task Processor.
2 Context-click the Task Processor, and select Stop from the context menu.
The Task Processor will stop after a few moments. When the Task Processor has stopped, the icon will have static horizontal stripes running through it.
|
You can re-activate it by context-clicking it and selecting Start from the context menu.
To restart a Task Processor
1 In the System Overview, locate the active Task Processor.
2 Context-click the Task Processor, and select Restart from the context menu.
While the Task Processor is restarting, the icon will have moving horizontal stripes running through it.
 |
To put an Output Task Processor offline
1 In the System Overview, locate the active Output Task Processor.
 |
2 Context-click the Task Processor, and select Put Offline from the context menu.
The Task Processor is colored blue to indicate that it is offline.
 |
To put an Output Task Processor online
1 In the System Overview, locate the offline Output Task Processor.
Offline Task Processors are colored blue.
2 Context-click the Task Processor, and select Put Online from the context menu.
The Task Processor comes back online, and the blue shading is removed from the icon.
To print an exposure test page for platesetters
When you first start to use your platesetters, you should submit an Exposure Test job to check the output and to select the engine’s best exposure settings. You should continue periodically to submit Exposure Test jobs to make sure that the engine is still producing good quality output.
NOTE: This option is currently supported only for the Galileo and XCalibur platesetters.
1 Select the System Overview.
2 Select your platesetter.
3 Double-click the Linearization Curves icon in the Resources pane.
 |
The Linearization Curves overview appears. In the upper pane, you see all of the available Linearization Curves for the selected platesetter.
4 Click the Exposure... button (only available for Galileo and XCalibur platesetters).
The Exposure Parameters dialog box is displayed. The name of the selected engine is displayed in the title bar of the dialog box.
You will see a list of resolutions at which you can print an exposure test. For each resolution, you will see default frequency and exposure settings. If you wish, you can change these default settings.
5 To change the frequency and exposure settings:
•Select a resolution, and click the Edit button:
 |
The Resolution Test Settings dialog box is displayed.
•Click the Frequency list, and select one of the available frequencies.
•Enter an Exposure setting.
•Click OK to return to the Exposure Test dialog box.
6 Use the check boxes in the Print column to select one or more of the available resolution settings.
7 Click the Print button.
The Exposure Test dialog box is closed, and test pages are printed out on the engine at the selected resolutions. The print date is automatically added to the test pages.
In the Job List, all exposure tests are grouped under the same order number called “Exposure Test”. The job name of the test file to be printed is called “<device name> Exposure Test”.
doc. version 6.1.1