Smart Print Controller OPC API
Smart Print Controller v6.0.0.8708, Copyright (c) 2026 Hybrid Software Helix Ltd. All rights reserved.
Overview
Smart Print Controller provides a user with two conceptual methods of operations:
-
Engineer - Installation and setup.
-
Operator - Manage job submission and review progress.
This 'operator' level of operation can be driven from external clients using an industry-standard interface.
When the Open Platform Communications (OPC) server in Smart Print Controller is enabled an OPC node tree is published. The top-level nodes in this tree represent grouped areas of state and functionality. For example, the Servers section allows:
-
the RIP Server list to be enumerated.
-
the server connection status to be examined.
-
all servers to be restarted.
-
...and more.
Certificates
Communication between OPC UA clients and servers require both parties to possess their own application certificate. To enable further communication each party must trust the opposing certificate. This trust can be established automatically, programmatically or manually depending on the application's configuration or implementation. The certificate for Smart Print Controller can be found in %programdata%\Hybrid Software Helix\Smart Print Controller\App Certificates\certs should you need to copy it to the Trusted Peer Certificate folder. In this release it is a Self Signed Certificate issued by and for Smart Print Controller.
OPC Nodes
The OPC node mechanism will report when any state changes, allowing clients to react accordingly.
While most exposed values can be read by a client, write-access (or calling a method to request a state change in Smart Print Controller) requires External Control to be granted (See App.IsExternalControlActive). This is an action explicitly performed by the Smart Print Controller operator, resulting in control of the application to be given to the OPC client.
Server Mode
If Smart Print Controller is launched with a /ServerMode command-line argument the application will be launched minimized, with OPC automatically enabled and External Control granted. Additionally, /Silent will disable the application splash screen and any taskbar messages that would otherwise be displayed.
Setting App.ServerModeLocked will ensure the application window stays minimized, with no option to be restored to the screen.
OPC Methods
Many published OPC method nodes return a String value indicating their success or error state. In all such cases a check for Success indicates success, and any other value indicates an error.
|
Return Value |
Description |
|---|---|
|
|
The request completed successfully. |
|
|
The media's printer profile differs from the 'active' profile. |
|
|
Direct printing cannot interrupt an active print run. |
|
|
At least one server is required for printing. |
|
|
Cannot execute the request. (External control not granted?) |
|
|
The HD connection(s) must be connected or disconnected - Not pending. |
|
|
Failed to update the HD configs to the values required for printing. |
|
|
Failed to restore the HD configs to the original values. |
|
|
The PDF could not be preprocessed. |
|
|
The PDF was preprocessed, but was invalid (E.g. It contains non-embedded fonts). |
|
|
The print run failed to start. |
|
|
Failed to submit the job to the server(s). |
|
|
The job was submitted, but failed to print. |
|
|
The specified item was not found. |
|
|
A command could not run because its execution criteria was not met. |
|
|
The print bar does not appear in the printer profile. |
|
|
Failed to load an application SPC configuration. |
|
|
The conditions needed to perform the action were not satisfied. |
|
|
The specified server is disabled. |
|
|
One or more of the parameters were invalid. |
|
|
Invalid page range or document repeat. |
|
|
Failed to set the page range of a job. |
|
|
Failed to apply vertical slicing to a job. |
|
|
The requested operation failed to succeed. |
Any methods returning data (for example JSON or comma-separated values) will be explicitly documented. Callers should validate returned data format to determine success (otherwise one of the above errors may be returned).
Any methods listed in this documentation include details about required parameters (if any) and return values.
In the event of an error, please see the Smart Print Controller log file for more information.
OPC Client Library
The following documentation provides guidance on using the Traeger Industry Components GmbH OPC client library for software developers working with Smart Print Controller.
Configuring Custom Message Sizes
The default maximum message sizes used by OPC clients to communicate to the server are sufficient for most use cases. However, to ensure transfer of larger data packets it may be necessary to configure the OPC client with custom values.
For example:
Client = new OpcClient();
Client.Transport.MaxArrayLength = 1024 * 1024 * 50;
Client.Transport.MaxBufferSize = 1024 * 1024 * 50;
Client.Transport.MaxMessageSize = 1024 * 1024 * 50;
Client.Transport.MaxStringLength = 1024 * 1024 * 50;
See here for more information.
Adjusting Communication Timeouts
OPC clients regularly verify the responsiveness of the connection to the OPC server. However, in certain circumstances where the system is under heavy load, maintaining a responsive connection might not always be possible. To mitigate potential issues under such conditions, it is recommended to increase the default communication timeouts.
The example below demonstrates how to adjust the default values:
var defaultTimeOut = (int)TimeSpan.FromMinutes(10).TotalMilliseconds;
Client = new OpcClient
{
// Don't auto-disconnect - Dispose the client to explicitly disconnect.
DisconnectTimeout = int.MaxValue,
KeepAlive = { Interval = defaultTimeOut },
SessionTimeout = defaultTimeOut,
OperationTimeout = defaultTimeOut,
ReconnectTimeout = defaultTimeOut
};
Please note that the provided examples serve as illustrations, and it's important to tailor the configuration to your specific requirements.
SPCSet
SPCSet is the top-level set containing all available OPC nodes. Immediately underneath this root-level node are a categorized collection of sub-nodes, each encapsulating a different area of behavior.
|
Section Name |
Description |
|---|---|
|
State relating to the currently active job. |
|
|
State relating to the currently active media. |
|
|
State relating to all jobs in the Waiting/Print/Completed queues. This tree dynamically includes children named from the GUID of each known job. |
|
|
State relating to all available media. |
|
|
State relating to the selected media (See |
|
|
State relating to the entire application. |
|
|
State relating to job cost estimation. |
|
|
State relating to available memory on the local machine and the memory required for the local RIP to function. |
|
|
State relating to the optional PageSubmitter plugin. |
|
|
State relating to the active print bars. |
|
|
State relating to the active printer profile. |
|
|
State relating to the print run. |
|
|
State relating to the print configuration (Applies to both media sides). |
|
|
The print configuration specific to media side 'A'. |
|
|
The print configuration specific to media side 'B'. |
|
|
State relating to the collection of RIP Servers. |
|
|
State relating to the offline Service RIP. |
|
|
Describes the collection of nodes representing a single job, positioned as a child of the |
|
|
State relating to Streamline Direct technology. |
|
|
State relating to the behavior of the Waiting queue. |
ActiveJob
State relating to the currently active job.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
Number of copies to print.
|
|
|
|
No |
Page number of the current processed page. |
|
|
|
No |
Unique job descriptor. |
|
|
|
No |
Whether or not the job can have lead in and/or lead out pages. |
|
|
|
No |
The result after running job font analysis. |
|
|
|
No |
Whether or not the job has been Autotuned. |
|
|
|
No |
Whether modifying operations (changes to copy count, job editor, ...) are allowed or not.
|
|
|
|
No |
Whether the job contains pre-RIPped pages. |
|
|
|
No |
Whether Streamline Optimize has processed the job. |
|
|
|
No |
A JSON string representing the data collected during the job cost estimation process. |
|
|
|
No |
The job ID received from the .complete file. |
|
|
|
No |
Property which can be used to group related jobs. |
|
|
|
No |
The job part ID received from the .complete file. |
|
|
|
No |
Property which can be used to attach arbitrary state to a job.
|
|
|
|
No |
Count of the lead in pages. |
|
|
|
No |
BASE64-encoded representation of the lead in page thumbnail PNG data. |
|
|
|
No |
Count of the lead out pages. |
|
|
|
No |
BASE64-encoded representation of the lead out page thumbnail PNG data. |
|
|
|
No |
The job name (from the original job file name). |
|
|
|
No |
Page count of the document. |
|
|
|
No |
Page height (mm). |
|
|
|
No |
Page width (mm). |
|
|
|
No |
The Streamline Direct predicted line speed (m/min). |
|
|
|
No |
The Streamline Direct predicted line speed (Status indicator).
|
|
|
|
No |
A comma-separated list of issues indicating if a job is printable, with the most serious being |
|
|
|
No |
Original producer of the PDF. |
|
|
|
No |
The page number at which to start printing the job. (Default: |
|
|
|
No |
When the job started printing (ISO 8601). |
|
|
|
No |
The intended media to use when printing the job. |
|
|
|
No |
BASE64-encoded representation of the job thumbnail PNG data. |
|
|
|
No |
Page count of the printed document ( |
ActiveMedia
State relating to the currently active media.
Details
The active media is the one actually being used to print.
The selected media (See AllMedia.SelectedName) is the one highlighted in the application UI.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
Whether color management (E.g. ICC profiles) is enabled.
|
|
|
|
No |
The date that the PrintFlat calibration was applied to each colorant, if applicable.
|
|
|
|
No |
This intent overrides all CMYK images. This setting also applies to gray images when |
|
|
|
No |
Collection of colorant calibration curves.
|
|
|
|
No |
Collection of supported colorant names. |
|
|
|
No |
Whether to process gray with CMYK color management. |
|
|
|
No |
Description of the media. |
|
|
|
No |
Name of the media's device emulation ICC profile. (See |
|
|
|
No |
Whether the device emulation ICC profile will be used. |
|
|
|
No |
Whether or not a PrintFlat Calibration has been applied to each colorant.
|
|
|
|
No |
Name of the media's input CMYK ICC profile. |
|
|
|
No |
Name of the media's input Gray ICC profile. (See |
|
|
|
No |
Name of the media's input RGB ICC profile. |
|
|
|
No |
Whether to keep text black. |
|
|
|
No |
This is the default rendering intent. The rendering intents in the document overrides it.
|
|
|
|
No |
The active media name. |
|
|
|
No |
Name of the media's output ICC profile. |
|
|
|
No |
Whether to override the color management specified in the PDF. |
|
|
|
No |
Whether to preserve 100% black. |
|
|
|
No |
This intent overrides all RGB images.
|
|
|
|
No |
This is the Total Area Coverage for the job. |
|
|
|
No |
The media width in mm. |
AllJobs
State relating to all jobs in the Waiting/Print/Completed queues. This tree dynamically includes children named from the GUID of each known job.
Details
These OPC nodes are fully populated to a consistent state when the OPC server starts, apart from job GUIDs - These nodes are dynamically added and removed as jobs are added and removed to/from the workflow.
(If there are already jobs in the workflow, these GUIDs will exist when the OPC server starts.)
When a job is added to the Waiting queue a GUID node is created containing the job information (containing the same tag names as the ActiveJob node) and that GUID is added to the WaitingQueue array.
The job keeps the same GUID as is travels through the system, moving between the WaitingQueue, PrintQueue, and CompletedQueue arrays.
The GUID node is removed when the job is removed from the workflow.
See the SingleJob section for a description of all available job-level nodes.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
When enabled, jobs in the Waiting queue will automatically move to the Print queue.
|
|
|
|
Yes |
When enabled, the print run is automatically stopped when all jobs have been printed.
|
|
|
|
No |
Collection of ordered GUIDs representing the jobs in the Completed queue. |
|
|
|
No |
Count of node changes made to jobs within the Completed queue. |
|
|
|
No |
The GUID of the job open in Job Editor. An empty string means no job is open. |
|
|
|
Yes |
For internal use only.
|
|
|
|
No |
Collection of ordered GUIDs representing the jobs in the Print queue. |
|
|
|
No |
Count of node changes made to jobs within the Print queue. |
|
|
|
Yes |
When enabled, the print run will copy all jobs over before we start printing.
|
|
|
|
No |
Collection of ordered GUIDs representing the jobs in the Waiting queue. |
|
|
|
No |
Count of node changes made to jobs within the Waiting queue. |
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Cancel a job in the Print queue. (Requires external control) |
|
|
|
Cancel the selected jobs in the Print Queue. (Requires external control) |
|
|
|
Change the active media of the print run. (Requires external control) |
|
|
|
Change the target media of selected jobs from the Waiting queue. (Requires external control) |
|
|
|
Remove all jobs from the Completed queue. (Requires external control) |
|
|
|
Clear selected jobs from the Completed queue. (Requires external control) |
|
|
|
Clear selected jobs from the Print queue. (Requires external control) |
|
|
|
Clear selected jobs from the Waiting queue. (Requires external control) |
|
|
|
Remove all jobs from the Waiting queue. (Requires external control) |
|
|
|
Duplicate a job in the Waiting queue. (Requires external control) |
|
|
|
Duplicate a job in the Waiting queue with a new name. (Requires external control)
|
|
|
|
Duplicate a job in the Waiting queue with a new name and a set of selected pages. (Requires external control)
|
|
|
|
Duplicates the selected jobs in the Waiting Queue. (Requires external control)
|
|
|
|
Export one or more jobs to a new |
|
|
|
Finalize a previously uploaded Waiting Queue job and create the queue entry.
|
|
|
|
Returns per-page RIP timings (seconds) for a single completed job. (Requires external control)
|
|
|
|
Import one or more jobs from a |
|
|
|
Upload a Waiting Queue job file in chunks, ready for later finalization.
|
|
|
|
Copy selected jobs from the Completed queue to the Waiting queue. (Requires external control) |
|
|
|
Move selected jobs from the Print queue to the Waiting queue. (Requires external control) |
|
|
|
Move selected jobs from the Waiting queue to the Print queue. (Requires external control) |
|
|
|
Remove a job from any queue. (Requires external control)
|
|
|
|
Resubmit a job from the Completed queue to the Waiting queue. (Requires external control) |
|
|
|
Sends the selected jobs in the Waiting queue to the Pre-Press folder. (Requires external control) |
|
|
|
Open a job in Job Editor. (Requires external control)
|
|
|
|
Move a job from the Waiting queue to the Pre-Press folder. (Requires external control) |
|
|
|
Move a job from the Waiting queue to the Print queue. (Requires external control) |
|
|
|
Set the page range of a job, rebuilding the PDF with the pages specified. (Requires external control)
|
|
|
|
Applies vertical slicing to the job. (Requires external control)
|
AllMedia
State relating to all available media.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
The media group filter.
|
|
|
|
No |
Collection of all available media names.
|
|
|
|
Yes |
Call prior to using the |
|
|
|
Yes |
The selected media name (which may differ from the applied media name).
|
|
|
|
Yes |
User-definable comma-separated list of ink names to suppress. (Requires external control)
|
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Permanently delete the named media (Use with caution). (Requires external control)
|
|
|
|
Inspect the contents of a |
|
|
|
Install a new |
|
|
|
Install a new |
Files
|
Name |
Description |
|---|---|
|
|
Allows read/write access to an SMD file. (See |
NOTE OPC File nodes contain functions which allow access to file content:
-
Open(int fileAccess)- Open the file with the specifiedfileAccess(1:read,2:write), returning an integer file handle. -
Read(int fileHandle, int length)- Read data from an open file handle, returning an array of bytes. -
Write(int fileHandle, byte[] buffer)- Write/append data to an open file handle. -
Close(int fileHandle)- Close the file handle after use.
For more information see the OPC documentation.
AllMedia.SelectedMedia
State relating to the selected media (See AllMedia.SelectedName).
Details
Note that when setting new media properties the changes are set in the Smart Media immediately, but changes must be applied using App.ApplySettings() before they take effect on the server(s).
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
Whether color management (E.g. ICC profiles) is enabled.
|
|
|
|
No |
The date that the PrintFlat calibration was applied to each colorant, if applicable.
|
|
|
|
Yes |
This intent overrides all CMYK images. This setting also applies to gray images when |
|
|
|
No |
Collection of colorant calibration curves.
|
|
|
|
No |
Collection of supported colorant names. |
|
|
|
Yes |
Whether to process gray with CMYK color management.
|
|
|
|
Yes |
Description of the media.
|
|
|
|
No |
Name of the media's device emulation ICC profile. (See |
|
|
|
Yes |
Whether the device emulation ICC profile will be used.
|
|
|
|
No |
Whether or not a PrintFlat Calibration has been applied to each colorant.
|
|
|
|
No |
Name of the media's input CMYK ICC profile. |
|
|
|
No |
Name of the media's input Gray ICC profile. (See |
|
|
|
No |
Name of the media's input RGB ICC profile. |
|
|
|
Yes |
Whether to keep text black.
|
|
|
|
Yes |
This is the default rendering intent. The rendering intents in the document overrides it.
|
|
|
|
No |
The selected media name. |
|
|
|
No |
Name of the media's output ICC profile. |
|
|
|
Yes |
Whether to override the color management specified in the PDF.
|
|
|
|
Yes |
Whether to preserve 100% black.
|
|
|
|
Yes |
This intent overrides all RGB images.
|
|
|
|
No |
This is the Total Area Coverage for the job. |
|
|
|
Yes |
The media width in mm.
|
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Remove the print bar group scaling settings from the selected media. (Requires external control)
|
|
|
|
Save the print bar group scaling settings to the selected media. (Requires external control)
|
|
|
|
Allows the calibration curve associated with a known colorant to be modified. (Requires external control)
|
|
|
|
Install an ICC profile into the selected media. (Requires external control)
|
|
|
|
Install an ICC profile into the selected media. (Requires external control)
|
|
|
|
Install an ICC profile into the selected media. (Requires external control)
|
|
|
|
Install an ICC profile into the selected media. (Requires external control)
|
|
|
|
Install an ICC profile into the selected media. (Requires external control)
|
App
State relating to the entire application.
Details
Some features (such as job costing) require the use of an offline service RIP, allowing for background processing while other job actions are active.
If any RIP servers are currently defined to use 127.0.0.1, the service RIP will not be available (See OpcServiceRip).
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
Whether the application allows spot colors to be edited |
|
|
|
No |
The application's local Centralized Ink Library Location |
|
|
|
Yes |
List of spot colors in clipboard in serialized string form.
|
|
|
|
Yes |
The default 16 bit behavior, when the media does not define a 16 bit behvior.
|
|
|
|
No |
The edition of the application specified by the license. |
|
|
|
No |
Whether the application is allowing clients external control. |
|
|
|
No |
The folder in which job assets are located.
|
|
|
|
No |
The application product name. |
|
|
|
Yes |
The folder in which local RIP TIFF output is produced.
|
|
|
|
Yes |
Whether to lock the minimized status of the application UI when running in server mode.
|
|
|
|
No |
Tally of the total printed sheet count. |
|
|
|
No |
Describes the application version number. |
|
|
|
No |
The application's local Waiting queue folder. |
|
|
|
No |
The percentage of space used on the disk where the application's local Waiting queue folder is located. |
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Add a color to clipboard.
|
|
|
|
Apply the current application settings and update all RIP Server config files. (Requires external control)
|
|
|
|
Create an SPC support package file.
|
|
|
|
Request the application to shut itself down.
|
|
|
|
Load an SPC application configuration file. (Requires external control)
|
|
|
|
Load an SPC application configuration file (in chunks). (Requires external control)
|
|
|
|
Allows an OPC client to write an error message into the application log. |
|
|
|
Allows an OPC client to write an information message into the application log. |
|
|
|
Allows an OPC client to write a warning message into the application log. |
|
|
|
For internal use only. (Requires external control) |
|
|
|
Revert any pending application settings. (Requires external control) |
|
|
|
Allows an OPC client to register it has entered/exited a 'busy' state requiring 'external control'.
|
Files
|
Name |
Description |
|---|---|
|
|
Allows read-only access to the application log file. |
|
|
Allows read-only access to the created support package file. (See |
NOTE OPC File nodes contain functions which allow access to file content:
-
Open(int fileAccess)- Open the file with the specifiedfileAccess(1:read,2:write), returning an integer file handle. -
Read(int fileHandle, int length)- Read data from an open file handle, returning an array of bytes. -
Write(int fileHandle, byte[] buffer)- Write/append data to an open file handle. -
Close(int fileHandle)- Close the file handle after use.
For more information see the OPC documentation.
JobCosting
State relating to job cost estimation.
Details
Job cost estimation requires the use of a local service RIP, allowing for background processing while other job actions are active.
Changes to the state in this section are immediate and do not require an explicit 'Apply' action.
To generate a cost report from an SPC-queued job, call ProcessJob().
If successful, the JSON result will either be stored in the job's JobCostData property or in AvailableResults (depending on the parameters passed to ProcessJob()).
If the latter, the AvailableResults array will be updated once processing is complete, and a call to GetReportData() may be performed.
If the job succeeds, GetReportData() will return a JSON string.
If the job fails, GetReportData() will return an empty string.
If the job is cancelled (CancelJobFile()), the AvailableResults array will not be updated, and GetReportData() will not be required.
A scheduled job can be cancelled at any time by calling CancelJobFile().
External control is not required for job costing actions to be performed.
Clients may call App.SetClientIsBusy() to let SPC know its job costing feature is being used.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
A collection of GUIDs representing the completed tasks previously scheduled with a call to |
|
|
|
Yes |
The default unit of cost. |
|
|
|
Yes |
The default drop volume (picoliters) for each drop size, for each ink.
|
|
|
|
Yes |
The default cost of each ink (per liter), in the unit specified by |
|
|
|
Yes |
The default specific gravity of each ink. (The ratio of ink density to the density of water.)
|
|
|
|
Yes |
The default cost of the media per m². |
|
|
|
Yes |
Indication to the client job costing app that a request has been made to import the selected jobs. |
|
|
|
Yes |
Whether the job cost estimation feature is enabled. (See |
|
|
|
Yes |
The default unit used to determine cost.
|
|
|
|
No |
The shared memory requirement for job costing (in gigabytes).
|
|
|
|
Yes |
The cost to apply each time a service interval is encountered. |
|
|
|
Yes |
The media interval at which the service cost is applied. |
|
|
|
Yes |
Use optimized job analysis to decrease processing times. |
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
After calling |
|
|
|
This method may be called each time the |
|
|
|
This method schedules an SPC job for costing, given the SPC GUID of the job. (See AllJobs)
|
Memory
State relating to available memory on the local machine and the memory required for the local RIP to function.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
The currently available RAM (in gigabytes).
|
|
|
|
No |
The maximum memory required for a single RIP (in gigabytes).
|
|
|
|
No |
The required memory to allocate for shared memory for a single RIP (in gigabytes).
|
|
|
|
No |
The number of RIPs used.
|
|
|
|
No |
The state of the system's available RAM versus the RAM requirements of the RIP.
|
PageSubmitter
State relating to the optional PageSubmitter plugin.
Details
Automatically splits multi-page PDFs into smaller jobs for printing
This feature allows submission of specific page ranges from a single PDF file. Instead of printing an entire document at once, it can be split into separate print jobs.
For example, pages 1-5, pages 6-10, and so on. Each page range becomes its own job in the Waiting queue, making it easier to manage large documents or prioritize specific sections for printing.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
Gets the name of the active source job. |
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Load job file (in chunks).
|
|
|
|
Loads a job file directly from a file system path that is accessible to both the OPC server and client. |
|
|
|
Extract one or more pages from the currently open job and submit them to the Waiting queue. |
PrintBarGroups
State relating to the active print bars.
Details
Note that each print bar 'group' corresponds to a collection of print bars which use the same settings (BPP, resolution, etc).
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
The bits per pixel (BPP) of each print bar group. |
|
|
|
No |
The colorant list for each print bar group. |
|
|
|
No |
The number of print bar groups. |
|
|
|
Yes |
Whether a print bar group's output will be flipped horizontally.
|
|
|
|
Yes |
Whether a print bar group's output will be flipped vertically.
|
|
|
|
No |
The names of each print bar group. |
|
|
|
No |
The horizontal resolution (DPI) of each print bar group. |
|
|
|
Yes |
The horizontal page scale (%) of each print bar group.
|
|
|
|
No |
Which media side each print bar group relates to (A/B). |
|
|
|
No |
The plane numbers for each colorant in each print bar group. |
|
|
|
Yes |
The rotation of each print bar group.
|
|
|
|
No |
The vertical resolution (DPI) of each print bar group. |
|
|
|
Yes |
The vertical page scale (%) of each print bar group.
|
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Set a collection of failed nozzle numbers (1+) for a given print bar. |
PrinterProfile
State relating to the active printer profile.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
The PIN required to access the Engineer pane. The PIN must be comprised of four characters, each being a number, or it can be left empty. An empty PIN will mean a PIN is not required to access the Engineer pane. |
|
|
|
No |
A list of ink names defined in the printer profile. |
|
|
|
No |
Complementing |
|
|
|
No |
The printer line speed (m/min). |
|
|
|
No |
The printer manufacturer. |
|
|
|
No |
The type of media.
|
|
|
|
No |
The printer model. |
|
|
|
Yes |
The name of the active printer profile.
|
|
|
|
No |
Whether the print bars are horizontal to the printed page image. |
|
|
|
No |
The type of printer.
|
|
|
|
Yes |
Whether the page image should be rotated clockwise when the print bars are horizontal to the image.
|
|
|
|
Yes |
Whether automatic channel cloning is supported.
|
|
|
|
No |
Whether the printer supports color. |
|
|
|
No |
Whether the printer supports a QI vision system. |
|
|
|
No |
Whether the printer supports duplex. |
|
|
|
No |
A list of supported media widths (mm). |
|
|
|
No |
Whether the printer supports offline printing mode (RIP Ahead). |
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
For internal use only. |
PrintRun
State relating to the print run.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
The state of the print run Abort button.
|
|
|
|
No |
Whether the print run is currently active. |
|
|
|
Yes |
The maximum number of simultaneous jobs to submit for printing at any one time.
|
|
|
|
No |
The state of the print run Start button.
|
|
|
|
No |
The status of the print run.
|
|
|
|
No |
The state of the print run Stop button.
|
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Abort an active print run (Immediate). (Requires external control) |
|
|
|
Start an active print run. (Requires external control)
|
|
|
|
Stop an active print run (As soon as possible). (Requires external control)
|
PrintRunConfig
State relating to the print configuration (Applies to both media sides).
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
Whether to automatically append an information page to each printed job.
|
|
|
|
No |
The cue mark interval in mm. |
|
|
|
No |
The duplex mode.
|
|
|
|
Yes |
Indicates whether Apex renderer is enabled.
|
|
|
|
Yes |
Whether to add nozzle refresh bars onto the printed output.
|
|
|
|
Yes |
How many nozzle refresh pages to append to the job. ( |
|
|
|
Yes |
How many pages to process before inserting mid-document nozzle refresh pages. ( |
|
|
|
Yes |
How many nozzle refresh pages to add each time |
|
|
|
Yes |
Whether to add nozzle refresh pages into the printed output.
|
|
|
|
Yes |
How many nozzle refresh pages to prepend to the job. ( |
|
|
|
Yes |
Whether jobs are ripped, screened if they have been ripped, or are ripped and screened at once.
|
PrintRunConfig.ConfigSideA
The print configuration specific to media side 'A'.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
The number of active nozzles that the print bar has.
|
|
|
|
Yes |
The screen calibration justification ( |
|
|
|
Yes |
The screen calibration offset in nozzles.
|
|
|
|
No |
A hash representation of the nozzle configuration.
|
|
|
|
No |
The print position ( |
PrintRunConfig.ConfigSideB
The print configuration specific to media side 'B'.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
The number of active nozzles that the print bar has.
|
|
|
|
Yes |
The screen calibration justification ( |
|
|
|
Yes |
The screen calibration offset in nozzles.
|
|
|
|
No |
A hash representation of the nozzle configuration.
|
|
|
|
No |
The print position ( |
Servers
State relating to the collection of RIP Servers.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
The available Meteor config files.
|
|
|
|
No |
The available RIP Direct server config files.
|
|
|
|
No |
Which colorants each server can process. |
|
|
|
No |
Per-RIP Server connection statuses.
|
|
|
|
No |
The number of RIP Servers. |
|
|
|
No |
Which colorants each server will process. |
|
|
|
Yes |
Whether each server is enabled or disabled.
|
|
|
|
No |
Which media side each server relates to (A/B). |
|
|
|
No |
The Meteor configuration for each server.
|
|
|
|
No |
Overall connection status of all enabled servers.
|
|
|
|
No |
Per-RIP Server print run statuses.
|
|
|
|
No |
Per-RIP Server configurations. |
|
|
|
No |
Per-RIP Server paths. (E.g. |
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
Read the static (CPU model, ...) and dynamic (CPU load, ...) properties for the specified server. |
|
|
|
Restart all RIP Servers. (Requires external control) |
|
|
|
Sends a plugin-dependent command to a named RIP Server plugin. (Requires external control)
|
|
|
|
Allows a RIP Server log file to be selected for reading.
|
|
|
|
Set the Meteor config file for a specified server. (Requires external control)
|
|
|
|
Set the RIP Direct server config for a specified server. (Requires external control) |
Files
|
Name |
Description |
|---|---|
|
|
Allows read-only access to the selected RIP Server log file. (See |
NOTE OPC File nodes contain functions which allow access to file content:
-
Open(int fileAccess)- Open the file with the specifiedfileAccess(1:read,2:write), returning an integer file handle. -
Read(int fileHandle, int length)- Read data from an open file handle, returning an array of bytes. -
Write(int fileHandle, byte[] buffer)- Write/append data to an open file handle. -
Close(int fileHandle)- Close the file handle after use.
For more information see the OPC documentation.
ServiceRip
State relating to the offline Service RIP.
Details
The Service RIP provides functionality, including offline processing of jobs by rendering PDF pages into a contone image format for external manipulation and then re-embedding those images back into the original PDF.
The RipToContone() method is used to render each page of a PDF into a series of colorant-based contone TIFF images, which can be modified externally.
The EmbedContone() method re-embeds the modified images into the original PDF. The TIFF images and an accompanying job XML file (from RipToContone()) must be located in the specified input folder.
It is also possible to generate a PDF containing screened separations, allowing close examination of the output that would otherwise be sent to a press. See RipToScreenedPdf() for details.
This system enables asynchronous job processing, meaning jobs are queued and results are available later for retrieval. Clients can monitor the completion of these jobs via AvailableResults and retrieve detailed result data using GetResultData().
If any RIP servers are currently using 127.0.0.1, the Service RIP will not be available.
Clients may call App.SetClientIsBusy() to let SPC know its offline services are being used.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
No |
A collection of GUIDs representing the completed tasks previously scheduled with the Service RIP.
|
|
|
|
No |
Whether the service RIP is currently connected. |
|
|
|
No |
Whether the service RIP is required, but has failed to connect. |
Methods
|
Name |
Returns |
Description |
|---|---|---|
|
|
|
This method will trigger cancellation of the job identified with the job GUID. |
|
|
|
This method schedules an SPC job for processing, given the SPC GUID of the job. (See AllJobs)
|
|
|
|
This method may be called each time the |
|
|
|
This method schedules an SPC job for processing, given the SPC GUID of the job. (See AllJobs)
|
|
|
|
This method schedules an SPC job for processing, given the SPC GUID of the job. (See AllJobs)
|
|
|
|
This method schedules an SPC job for processing, given the SPC GUID of the job. (See AllJobs)
|
SingleJob
Describes the collection of nodes representing a single job, positioned as a child of the WaitingQueue, PrintQueue, or CompletedQueue nodes.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
Number of copies to print.
|
|
|
|
No |
When the job finished printing. (ISO 8601) |
|
|
|
No |
Unique job descriptor. |
|
|
|
No |
Whether or not the job can have lead in and/or lead out pages. |
|
|
|
No |
The result after running job font analysis. |
|
|
|
No |
Whether or not the job has been Autotuned. |
|
|
|
Yes |
Whether modifying operations (changes to copy count, job editor, ...) are allowed or not.
|
|
|
|
No |
Whether the job contains pre-RIPped pages. |
|
|
|
Yes |
Whether the user has selected the job in the UI.
|
|
|
|
No |
Whether Streamline Optimize has processed the job. |
|
|
|
No |
A JSON string representing the data collected during the job cost estimation process. |
|
|
|
No |
The job ID received from the .complete file. |
|
|
|
Yes |
Property which can be used to group related jobs.
|
|
|
|
No |
The job part ID received from the .complete file. |
|
|
|
Yes |
Property which can be used to attach arbitrary state to a job.
|
|
|
|
Yes |
Count of the lead in pages.
|
|
|
|
No |
BASE64-encoded representation of the lead in page thumbnail PNG data. |
|
|
|
Yes |
Count of the lead out pages.
|
|
|
|
No |
BASE64-encoded representation of the lead out page thumbnail PNG data. |
|
|
|
Yes |
The job name (from the original job file name).
|
|
|
|
No |
Page count of the document. |
|
|
|
No |
Page height (mm). |
|
|
|
No |
The total number of pages submitted to the output device.
|
|
|
|
No |
Page width (mm). |
|
|
|
No |
The Streamline Direct predicted line speed (m/min). |
|
|
|
No |
The Streamline Direct predicted line speed (Status indicator).
|
|
|
|
No |
Preprocessor status.
|
|
|
|
No |
A comma-separated list of issues indicating if a job is printable, with the most serious being |
|
|
|
No |
Original producer of the PDF. |
|
|
|
No |
The job position within the current queue (1+). |
|
|
|
Yes |
The page number at which to start printing the job. (Default: |
|
|
|
No |
When the job started printing (ISO 8601). |
|
|
|
No |
Up-to-date print status of the job.
|
|
|
|
Yes |
The intended media to use when printing the job.
|
|
|
|
No |
BASE64-encoded representation of the job thumbnail PNG data. |
|
|
|
No |
Page count of the printed document ( |
StreamlineDirect
State relating to Streamline Direct technology.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
The number of pages to sample when estimating print time.
|
|
|
|
Yes |
Whether jobs whose PredictedLineSpeedIndicator is Red - jobs that will not meet the Target Line Speed - can be sent to the Print Queue.
|
|
|
|
Yes |
Whether to Autotune jobs that have been estimated.
|
|
|
|
Yes |
Whether to estimate print time for jobs added to the Waiting Queue.
|
|
|
|
Yes |
The press's target line speed (m/min).
|
|
|
|
Yes |
The percentage of extra line speed above the defined maximum line speed that can be allowed as an estimate.
|
WaitingQueueOptions
State relating to the behavior of the Waiting queue.
Properties
|
Name |
Type |
Writable |
Description |
|---|---|---|---|
|
|
|
Yes |
Determines whether the SPC UI exposes the ability to lock/unlock jobs in the Waiting queue.
|
|
|
|
Yes |
Determines whether thumbnails will be generated for jobs added to the Waiting queue.
|
|
|
|
Yes |
Determines whether the Waiting queue only displays jobs which target the active media (See ActiveMedia).
|
|
|
|
Yes |
Determines whether the Waiting queue displays locked jobs.
|