PRINTDRIVE SUPPORT AND REFERENCE

December 2008
 PrintDrive Support and Reference
• The purpose for this presentation is to address general information
and requirements for PrintDrive, and to address problems commonly
reported from the field.

• This is not a full field service manual for PrintDrive, but rather is
provided as a supplement.

• References are provided to documents currently available in the

Agfa services library. These references are listed in RED:
“Title of document as displayed in services library”
Name of document itself.

• E.g.:
“TN Apogee PrintDrive S3 Windows 2003 Setup”
PDS3_Win2003_[60_00020561].pdf

• Please follow-up with the existing documents for more information.

2 Agfa Graphics: an introduction 30.12.08

 PrintDrive Support and Reference

• Sections addressed:
1. Engines and engine interface cards
2. PrintDrive SYSTEM Issues
3. Features sometimes overlooked in Update F
4. Duplex Proofing
5. What is “Allow Server Synchronization”?
6. PrintDrive LE
7. Diagnostic Tools
8. Suggestions for managing Apogee X/Prepress
import of PrintDrive S2 and S3 “backup” jobs
9. What to gather when debugging is needed…

3 Agfa Graphics: an introduction 30.12.08

Engines and engine interface cards
 Engines and engine interfaces

• Engine interface cards : Agfa – PCI & USB/APIS

• Engine interfaces : Agfa OEM and 3rd party

• Engines supported by PrintDrive & interface

used

• PrintDrive engine interface limitations

• Resources for analyzing APIS connection

problems

5 Agfa Graphics: an introduction 30.12.08

 Engine interface cards : Agfa - PCI
• PAC – PCI/APIS card, only used on 5V PCI.
• Part # printed on board 209734-502, -503, -504
• Requires APIS 37-to-62 pin adapter cable (wideÆnarrow APIS) when used with
older (narrow-APIS) engine.
• “PAC” printed on board.
• Order # 0028460501 / 0502 / 0503 / 0504 (board + 37-to-62 pin adapter cable)
• This was discontinued in 2001, and replaced by the UPAC board.

• UPAC – Universal PCI/APIS card, supports 5V (PCI) and 3.3v (PCI-X)

• Part # printed on board P00404-0501
• “UPAC” printed on board.
• Order # 0028460505 (UPAC board only)
• Order # 0028460506 (UPAC board + 37-to-62 pin adapter cable – needed for
narrow APIS engines)

• UPAC LV APIS – Universal PCI/APIS card, may be used in 3.3v (PCI-X)

and 5v PCI slots
• Part # printed on board P00404-0502
• Required for use with COB (common optics bed) imagers (e.g. Avalon, some
Xcalibur)
• “UPAC” printed on board, and “LV APIS” yellow label on end plate.
• Order # 0028460507 (UPAC LV APIS board only)

6 Agfa Graphics: an introduction 30.12.08

 Engine interface cards : Agfa - USB/APIS
• USB/APIS interface box
allows engine connection
when PCI board is not viable
due to lack of PCI bus on
PC.

• USB/APIS HD - used for Avalon and Xcalibur with COB.

• Part#: APIS HD USB w/ cables (Euro & US power cables) = 2Z+028-1179-200
• There are a limited inventory of the initial stock that have a separate part # for each power
cable. These are being sold out, replaced with 2Z+028-1179-200.
• Part#: APIS HD USB ASSEMBLY EURO = 2Z+028-1179-201
• Part#: APIS HD USB ASSEMBLY US = 2Z+028-1179-301
• This may be used in place of UPAC LV APIS board 209734-507

• USB/APIS standard - used for other APIS engines

• Part#: APIS Standard USB w/ cables (Euro & US power cables) = 2Z+028-1178-200
• This may be used in place of UPAC board 209734-506

• See document “TN USB-to-APIS module presentation”

7 Agfa Graphics: an introduction 30.12.08

 Engine interfaces : Agfa OEM and 3rd party
• Xitron PCI/PIF
• Used with Agfa Acento (OEM Screen) engines.
• Refer to Lieven Demaertelaere in Mortsel for latest download revisions
• Supports 5V & 3.3v, PCI & PCI-X
• No support for PCI-Express
• No support for Screen PCI/PIF card.

• SCSI
• Various vendor cards, adapters used for Agfa 3rd party devices.

• Cymbolic Science Inc (CSI)

• 5V PCI interface card used with Agfa Antares (OEM CSI). [product discontinued by Agfa.]
• No 3.3v, PCI-X, PCI-Express support

• Krause Laserstar
• 5V PCI card – proprietary from Krause
• Used with VLF Laserstar devices
• Limited install base

• TCP/IP
• Using network interface card (NIC) either on-board or through adapter bus.

• File system
• File based output device drivers may be used to interface with 3rd party engine workflows.

• null

8 Agfa Graphics: an introduction 30.12.08

 PrintDrive engines supported & interface used
• These engines all support either APIS or Wide-APIS, and may be used
with the following non-LV-APIS interface cards:
• PAC
• UPAC
• USB/APIS Standard
• Agfa AccuSet 1000 • Agfa SelectSet Avantra 20
• Agfa AccuSet 1500 • Agfa SelectSet Avantra 25
• Agfa AccuSet 800 • Agfa SelectSet Avantra 25E
• Agfa Galileo • Agfa SelectSet Avantra 25S
• Agfa Galileo S • Agfa SelectSet Avantra 25XT
• Agfa Galileo Talant • Agfa SelectSet Avantra 30
• Agfa Galileo Thermal • Agfa SelectSet Avantra 30E
• Agfa Galileo Thermal S • Agfa SelectSet Avantra 36
• Agfa Galileo VS • Agfa SelectSet Avantra 36S
• Agfa Galileo VS4 • Agfa SelectSet Avantra 44
• Agfa Galileo VXT • Agfa SelectSet Avantra 44E
• Agfa Phoenix 2000 • Agfa SelectSet Avantra 44S
• Agfa Phoenix 2000MP • Agfa SelectSet Avantra 44XT
• Agfa Phoenix 2250 • Agfa Xcalibur 45 (pre-v4.0 software)
• Agfa Phoenix 2250MP • Agfa Xcalibur VLF 50 (pre-XXT imager)
• Agfa Phoenix News • Agfa Xcalibur VLF 60 (pre-XXT imager)
• Agfa Phoenix NewsMP • Agfa Xcalibur VLF 70 (pre-XXT imager)
• Agfa SelectSet 5000 • Agfa Xcalibur VLF 80 (pre-XXT imager)
• Agfa SelectSet 5000 (2400) • Agfa Xcalibur VLF 83 (pre-XXT imager)
• Agfa SelectSet 7000

9 Agfa Graphics: an introduction 30.12.08

 PrintDrive engines supported & interface used
• These engines all require one of the following LV-APIS interface
cards:
• UPAC LV-APIS
• USB/APIS HD

• Agfa Avalon LF
• Agfa Avalon VLF
• Agfa Xcalibur 45 (with v4.0 software or later)
• Agfa Xcalibur VLF 50 (with XXT imager)
• Agfa Xcalibur VLF 60 (with XXT imager)
• Agfa Xcalibur VLF 70 (with XXT imager)
• Agfa Xcalibur VLF 80 (with XXT imager)
• Agfa Xcalibur VLF 83 (with XXT imager)

10 Agfa Graphics: an introduction 30.12.08

 PrintDrive engines supported & interface used
• Xitron PCI/PIF
• Agfa Acento E
• Agfa Acento S

• SCSI
• Agfa Palladio
• Agfa Palladio M
• FlatRite PF-R1050
• PolaProof
• Prediction 2230a
• TrendSetter

• Cymbolic Science Inc (CSI)

• Antares 1000
• Antares 1000 XT
• Antares 1600

• Krause Laserstar
• LaserStar LS 140C
• LaserStar LS 170C
• LaserStar LS 200C

11 Agfa Graphics: an introduction 30.12.08

 PrintDrive engines supported & interface used
• TCP/IP • File system
• AgfaJet GrandSherpa 50 • PDF Proofer
• AgfaJet GrandSherpa 64
• AgfaJet GrandSherpa 87 • PostScript Proofer
• AgfaJet GrandSherpaMatic • PostScript Proofer (Duplex)
• AgfaJet Sherpa • Tiff File
• AgfaJet Sherpa 2
• AgfaJet Sherpa 24 • Tiff File (Platesetter)
• AgfaJet Sherpa 24M • Kodak Approval XP2 (2400)
• AgfaJet Sherpa 43 • Kodak Approval XP2 (2540)
• AgfaJet Sherpa 44M
• AgfaJet Sherpa 54 • Kodak Approval XP4 (2400)
• AgfaJet Sherpa 62 • Kodak Approval XP4 (2540)
• AgfaJet SherpaMatic 43
• AgfaJet SherpaPlus
• Epson 10000 • HP DesignJet 1050 (RTL data)
• Epson 4800 • HP DesignJet 2500CP (RTL data)
• Epson 4880 • HP DesignJet 3500CP (RTL data)
• Epson 7800
• Epson 7880 • HP DesignJet 750C (RTL data)
• Epson 9800
• Epson 9880
• Epson X800 (Duplex)
• Epson x880 (Duplex) • null
• HP DesignJet 1050
• HP DesignJet 2500CP
• PrintDrive Demo
• HP DesignJet 3500CP
• HP DesignJet 750C
• Impress 2000
• Impress 750

12 Agfa Graphics: an introduction 30.12.08

 PrintDrive engine interface limitations

• No support for the Screen PCI/PIF card

• No support for AvalonN
• No support for PCI-Express
• Cannot connect to APIS engine on PCI-Express
platform
• Cannot connect to Acento on PCI-Express platform
• No support for additional HP proofers. Limited
to 4-color models only.
• No support for direct driver to HP SpinJet
• configurations have been set up using the RTL data
to print spooler
• No support for additional Epson proofers or color
models

13 Agfa Graphics: an introduction 30.12.08

 UPAC issues with non-TKS systems

• The UPAC boards are only qualified systems available

from the Agfa turn-key-solutions (TKS) portfolio.
• While using the UPAC on other vendor or model PC may
be functional, there have been throughput problems with
the UPAC board on the PCI bus some non-TKS HP
Proliant systems.
• USB/APIS may be used as a last alternative to resolve
these issues.

• RECOMMENDATION: Advise customers to

select models that are included in the Agfa TKS
portfolio.

14 Agfa Graphics: an introduction 30.12.08

 FIELD SUPPORT: “NRB” and “DR”
• PrintDrive posts two statistics in the job log for each image processed to an
output device. These performance metrics are logged for diagnostic
analysis when problems are observed. These are approximations and
should not be interpreted as absolute.

• “DR” – data rate (in MB/sec) measured in the transfer of image data to the
output device. The data rate is controlled by the speed of:
• speed of the imager (how fast is engine demanding data)
• speed of the interface to the engine (PCI card, APIS)
• size of image (resolution, width, height)
• rate at which PrintDrive is preparing data

• DR with high-resolution devices

• The data rate will be relatively constant on an engine when processing same-
size images.
• Some deviation (e.g. 7.6MB/sec vs. 7.4 MB/sec is inconsequential).
• If DR appears low and, and throughput is less than expected:
1. check engine components (laser power, electronics)
2. Make sure that the interface is being used in a qualified TKS system. For example, if
UPAC is used in non-TKS system, poor performance may be measured.
3. Replace interface card (e.g. defective UPAC)
4. Replace APIS cable
5. If NRB’s are listed … see next slide.

15 Agfa Graphics: an introduction 30.12.08

 FIELD SUPPORT: “NRB” and “DR”
• “NRB” – “not ready buffer”
• PrintDrive passes data to the output device in segments (strips).
• PrintDrive uses a multi-threaded design to ensure that image data is read from
disk, processed (DQS, finishing marks, web-growth, plate pairing, etc), and
ready to transfer when the output device is seeking more data.
• The NRB statistic indicates how many times PrintDrive failed to prepare a
segment of data when the device was ready for more. In effect, this
suggests that PrintDrive is not keeping up with the demand of the device.

• NRB’s with high-resolution devices

• Typically no NRB’s are registered, however, it is not uncommon for see a few.
• If a significant number of NRB’s are seen, and throughput is less than expected:
1. slow access to the disk subsystem – defragment disks, check disk controllers
2. non-optimal orientation of DQS pages requiring excessive rotation – make sure that
pages are rendered in a rotation that matches how they will be imposed in the flat.

• NRB’s with proofing devices

• It is not uncommon for NRB’s to be registered for proofing devices, since the work to
prepare the data is extensive and the buffering and data transfer capacity to the
proofing devices is low.
• We don’t worry about NRB’s on proofers.

16 Agfa Graphics: an introduction 30.12.08

 FIELD SUPPORT: APIS command tracing
• The PrintDrive “APIS” driver saves a trace of all APIS
commands sent between the driver and the engine. This
is stored in a circular file (max size 5MB), with each entry
date/time stamped. This continuous logging imposes no
overhead to the throughput.

• The APIS command trace file is found in the install path

of the PC connected to the engine.
C:\PrintDrive\Log\APIS_myPC^myAvalon.txt
• The file is named with the template:
APIS_<hostname>^<PrintDrive device name>.txt

• When a problem is encountered, the following items

should always be delivered to RND:
• APIS command trace file
• Examples of error plates (if problem is related to imaging)

17 Agfa Graphics: an introduction 30.12.08

 FIELD SUPPORT: APIS command tracing
• The APIS command interface allows asynchronous transfer of commands between the driver and the engine. This
is an Agfa proprietary syntax, with different commands specified for different engine models. The APIS command
specifications are available under document management control by RND in Mortsel.
• The syntax is consists of commands surrounded by brackets “{ … }”, with the first two characters identifying the
source and target for each message. “{SR” is the prefix for messages sent from the driver, “{RS” is the prefix for
messages sent from the engine to the driver. E.g. driver checking status of engine:
{SRSS} – driver queries the engine status
{RSSH02} – engine replies “idle” (error code 02)
{SRSS} – driver queries the engine status
{RSSH04} – engine replies “off-line” (error code 04)
{SRSS} – driver queries the engine status
{RSSH01} – engine replies “fatal error” (error code 01 )

• APIS commands are sent by the driver to query the engine configuration. E.g.:
{SRGX2;6} – driver queries info about plate id 6
{RSPA0;2400;51872;61512;2;12;3;651x549x12AZ;190;0;2} – engine replies that plate is named
“651x549x12AZ”, 51872 pixels (@2400dpi) in fast scan, 61512 pixels in slow scan

• APIS commands are sent to initiate plate loading

{SRFP18;51;2400;0;0;0;0;0} – driver requests plate id 18, and assigned sequence number 51, used to track update notifications
{RSMP25000051} – first notification from engine indicates that plate with sequence # 51 loaded successfully (status code 25)
… imaging proceeds …
{RSMP25000051} – second notification from engine indicates that plate sequence # 51 completed imaging ( status code MP25)
… OR …
{RSMP26000051} – engine notification that plate with sequence # 51 FAILED to load (MP26)

• APIS commands are issued to set up the imaging: E.g.

{SRJNColor Brochure} – driver assigned job name Color Brochure
{SRII1 F Cyan} – driver assigns image information – sig 1, front, Cyan sep
{SRSP03068032} – driver specified image size in fast scan dimension = 68032 pixels
{SRBT} – driver specifies “begin take”
{SRET049152} – driver specifies image size in slow scan dimension =49152 pixels
{RSMG03} – engine notification that it is an imaging status … at this point the image data is transferred to the engine
{RSMG09} – engine notification that it has COMPLETED imaging
{RSMG02} – engine notification that it is an IDLE status
{RSMP25000051} – engine notification that plate with sequence #51 has finished processing

18 Agfa Graphics: an introduction 30.12.08

 FIELD SUPPORT: APIS command tracing
• The Xcalibur and Avalon systems require a complication exchange of APIS commands between
the driver and the engine in order to manage:
• concurrent loading of multiple plates
• out of plate conditions with the auto loader systems

• A problem from a field installation may be that the plate load started, the plate went into the drum,
but then imaging never started. With knowledge of when this happened, you may review the APIS
trace file to confirm the expected results:

{SRFP30;23;2400;0;0;0;0;0} – driver requests plate id 30, assigning sequence # 23

{RSMP30000023} – engine notification that sequence # 23 is in process, not ready yet
{SRFP30;24;2400;0;0;0;0;0} – driver requests plate id 30, assigning sequence # 24
… arbitrary amount of time passes …
{RSMP25000023} – engine notification that sequence # 23 is ready to image

• Things to check:
• Q: At some point after the plate load command (FP) is issued with a sequence #, does the engine
issue an MP25 for the sequence number?
• A: If NO, then there is a problem with the engine – check OCT and engine error recovery status
• A: If YES,
• Q: Is the sequence number the expected value? (disregard MP25 message for plates being
imaged in front of this one)
• A: If NO, then there is a problem with the engine software – check for latest version (Gary
Carlson, Stein Bratland).
• A: If YES, then there is a problem with PrintDrive (not recognizing that plate is ready).
• Verify that PrintDrive Update F Service Pack 4 is installed.
• Restart the PrintDrive device. If necessary restart the AGFAOutputControl service.

19 Agfa Graphics: an introduction 30.12.08

 FIELD SUPPORT: APIS video tracing
• For diagnostic purposes, the capability to benchmark the image
transfer events may be enabled. This should only be used to
analyze problems that may be related to the UPAC or USB/APIS.
• To enable this for an output device,
• Run “RegEdit”
• Browse to the device entry
• Add key “VidEvtLog”
• Set default value of key to “1”
REGEDIT4
#--------------------------------------------------------
# Cut and paste this into a text file with .reg extension.
# Edit <engine name here> with the actual PrintDrive device name being used
[HKEY_LOCAL_MACHINE\SOFTWARE\Agfa\PrintDrive\OutputDevices\<engine name here>\VidEvtLg]
@="1"
#--------------------------------------------------------

• Restart PrintDrive device.

• Video timings for each data transfer will be logged to a separate file.
• NOTE: only use this when necessary. It will create a large number
of files as plate imaging continues.

20 Agfa Graphics: an introduction 30.12.08

 FIELD SUPPORT: APIS video tracing
• The APIS video trace file is found in the install path of the PC connected to the engine.
C:\PrintDrive\Log\APIS_PAC_10-20-21_my job name_1 F Black.txt
• The file is named with the template:
APIS_<interface type>_<time stamp>_<job name>_<image ID>.txt

• PrintDrive delivers the plate image to the device as a series of

buffers.
EXAMPLE (with small image) • The video log traces the following for each buffer (use 2nd line of file to
0 60718 1210368 the left as an example):
• timestamp (ms) @ before buffer transfer (e.g. 60734 ms)
60734 61281 1210368
• timestamp (ms) @ after buffer transfer (e.g. 61281 ms)
61281 61828 1210368 • size of buffer (in bytes) (e.g. 1210358 bytes)
61843 62390 1210368
62390 62953 1210368 • Important statistics to gather from this (use 2nd and 3rd lines of file to
62953 63500 1210368 the left as an example)::
63500 64062 1210368 • #ms to transfer a buffer = “after” time – “before” time (e.g. 61281 – 60734 = 547 ms)
• #ms between buffer transfers = “before” time for current buffer minus “after” time for
64062 64609 1210368 previous buffer (e.g. 61281 – 61281 = 0 ms)
64609 65172 1210368 • What to expect:
65172 65718 1210368 • the time to transfer each buffer should be fairly consistent
65718 66281 1210368 • the time between buffer transfers should be low or zero.
66281 66828 1210368 • Possibly problems to look for:
66828 67390 1210368 • If a buffer transfer time is erratic then there is a problem with the interface
card, or with the APIS interface on the engine side.
67390 67937 1210368 • If the time between buffer transfers is high, then PrintDrive is not able to
67937 68500 1210368 prepare the image data fast enough for the engine. This should coincide
with NRB’s in the job log.
68500 69047 1210368
• In either case, you may observe stop/start events on the engine.
69047 69609 1210368
69609 70156 1210368 • Avoid false interpretations
70156 70703 1059072 • Ignore the first few buffer transfers as the engine will transfer this to an
internal buffer, but may not image immediately. This may appear as a slow
data transfer.
• The last buffer is typically a smaller size than the rest of the buffers.

21 Agfa Graphics: an introduction 30.12.08

PrintDrive SYSTEM Issues
 PrintDrive SYSTEM Issues

• Latest software

• Manual installation steps

• Managing PrintDrive on the network

• What to do if hostname or IP address changes on

PrintDrive server?

• Ports used by PrintDrive

• Using PCD (legacy hardware compression)

23 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Latest software
• The PrintDrive software is installed with the following:
• PrintDrive Series 3
only available on CD-ROM
• PrintDrive Series 3 Update F
“SW Apogee PrintDrive Series 3 Update F”
Apogee Printdrive Series 3 UpdateF.zip

• PrintDrive Series 3 Update F Service Pack 4

“SW Apogee PrintDrive S3 Update F Service Pack4”
PDS3_UpdF_SP4.zip

[It is NOT NECESSARY to install prior service packs. ServicePack4 is ALL-INCLUSIVE]

• PrintDrive Proofing Resources V4

“SW Apogee PrintDrive S3 Update F Proofing Resources V4”
PDS3_UpdateF_Proofing_Resources_v4

• Windows Vista support for PrintDrive Remote Pilot

“SW Apogee PrintDrive S3 Vista Supplement”
PDS3_Vista_Supplement.zip

• The Agfa Services Library has many other items including outdated software (e.g.
Update D, Update E), temporary patches (e.g. various Update E hot fixes, patches),
and supplemental files (e.g. the original SW PrintDriveS3 UpdF HF Proofing
Resources)
• None of these files are needed if installing with latest PrintDrive software.

24 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Manual installation steps (Win 2003)

• The PrintDrive installer creates a network share where

common data is accessed from remote PrintDrive
components (PrintDrive Pilots, Satellites)
• With Windows 2003 and Windows XP it is necessary to
follow each step in a set of instructions available in:
“TN Apogee PrintDrive S3 Windows 2003 Setup”
PDS3_Win2003_[60_00020561].pdf

• NOTE: It is not uncommon for problem calls directed to

engineering to be due to one or more steps excluded
when following these setup requirements.

25 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Manual installation steps (Win 2003)

• Failure to follow each of the steps described in

the Tech Note may result in the following
problems:
• proofing devices error during output, cannot access
color profiles, ink tables
• digi-control wedge image is not showing up on the
finishing marks
• PrintDrive Satellite devices error during output,
cannot access raster data

26 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Importance of user credentials
• The PrintDrive Pilot and Apogee Prepress PrintDrive TP run as applications
with the current user’s credentials.
• Both of these attempt to access the PrintDrive job files directly through the
UNC address of the PrintDrive Raster Data directory (e.g.
\\myHost\PrintDrive Raster Data).

• It is necessary that the current user have credentials that allow access to
the PrintDrive Raster Data directory.
• This is common with user accounts that are common across multiple computers
or users that are configured in a domain.
• Credentials also may be established by mapping a network share by IP address
on the PrintDrive Raster Data computer to a local drive letter, and providing a
supported user name and password recognized by that computer.
• NOTE: It is important to map the network share by IP address, and not by
hostname.

• If user credentials are not established, the following problems may be

observer:
• No thumbnail images displayed in the PrintDrive Pilot.
• Errors when processing through the Apogee Prepress PrintDrive TP

27 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Oops! PrintDrive Hostname or IP address changed!

• PrintDrive creates the “PrintDrive Data Share” as a network share to hold

common files (proofing resources, finishing mark files, web growth profiles).
C:\PrintDrive\PrintDrive Data Share
• An internal database is initialized with the UNC address of the PrintDrive
Data Share subfolders. These are used by PrintDrive components to
access the common data.
\\myPrintDrive\PrintDrive Data Share\ ...

• When the hostname of the PC is changed (e.g. “myPrintDrive” Æ

“PD_AvalonLF”) the pathnames in the internal database are no longer
valid. Hence, the common data is no longer accessible.

• As a result the following problems will appear

• proofing devices error during output, cannot access color profiles, ink tables
• digi-control wedge image is not showing up on the finishing marks
• User cannot select color profiles, ink tables, or other common files from
PrintDrive Pilot.

• To correct this:
• Run the new utility “PrintDrive_Hostname_and_IP_Address_Fixer.exe”, or
• Re-install PrintDrive software after hostname has been changed.

28 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Accessing MAC OSX 10 or Unix systems

• Customers may use a MAC OSX 10 or Unix

system for:
• Storing raster data or back up data
• Open connect input hot folder

• See technical note describing these settings:

“TN Apogee PrintDrive S3 Unix and Mac OSX File Sharing Setup”
PDS3_Unix&Mac_File_Sharing.pdf

29 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Ports used by PrintDrive
• The services operating on the Port # Used by …

PrintDrive Server and PrintDrive 1600 AGFAJobControl

Satellites use the ports as listed. 1601 AGFAPrintDrive

1607 AGFAOutputControl2
• These are all fixed with the 1608 AGFAOutputControl
exception of the range of ports
1610 AGFAApisIn
used by the “AGFAOutputControl”
& “AGFAOutputControl2” 1611 AGFAInkDrive

services. 1612 AGFAImport

1615 AGFAFileService

• PrintDrive will not operate 1666 AGFAJobControl

correctly if other applications have 1667 AGFAPrintDrive
reserved these ports on the same
1668 AGFAOutputControl
system.
1670 AGFAApisIn

1671 AGFAInkDrive
• Despite this limitation, we have
only had a few instances where a 1672 AGFAImport
conflict occurred. In these cases, 1673 AGFAFileService
it was with the range of ports used 1674 AgfaPdfRip
by the “AGFAOutputControl” &
1675 AGFAOutputControl2
“AGFAOutputControl2” services.
7000 - 7099 AGFAOutputControl

7100 - 7199 AGFAOutputControl2

30 Agfa Graphics: an introduction 30.12.08

 SYSTEM: Ports used by PrintDrive
• The range of ports used by the “AGFAOutputControl” &
“AGFAOutputControl2” services may be re-mapped in RegEdit if a conflict
occurs.
• A port conflict may be the problem if:
• a device fails to display status information in the PrintDrive Pilot device “Status”
view.
• a device fails to start …and all other corrections have been exhausted.
• This is not common, but has been necessary a few times.

• Edit the “PortLowerLimit” and “PortUpperLimit” of the appropriate service (as

described below).
REGEDIT4
#--------------------------------------------------------
# Cut and paste this into a text file with .reg extension.
# Edit the "PortLowerLimit" and "PortUpperLimit" as needed
[HKEY_LOCAL_MACHINE\SOFTWARE\Agfa\PrintDrive\AGFAOutputControl]
"PortLowerLimit"="7000"
"PortUpperLimit"="7099"

[HKEY_LOCAL_MACHINE\SOFTWARE\Agfa\PrintDrive\AGFAOutputControl2]
"PortLowerLimit"="7100"
"PortUpperLimit"="7199"
#--------------------------------------------------------

31 Agfa Graphics: an introduction 30.12.08

 System : PCD / Hardware Compression
• The PCD (hardware compression / decompression) board that was developed for use
with PrintDrive 1.0 and 2.0 to compress TIFF files and backup jobs
• There is no “software” decompression available to process jobs that were created
using the PCD. In other words, if you used a PCD to create the job you need a PCD
to restore it on a PrintDrive.
• For normal job processing, PrintDrive Series 3 does not use the legacy PCD.

• Limitations
• Use of the PCD with PrintDrive Series 3 is only recommended for attempting to restore jobs
that were originally saved from Series 1 or 2 using hardware compression.

• Driver Installation
• PCD driver is installed automatically into the system32/drivers directory in a usable form by
the PrintDrive installer.
• No plug & play driver for Win2000. Disregard “Found New Hardware” messages.

• STATUS: Windows 2000

• The driver is installed automatically by the PrintDrive installer.
• Disregard the Windows “Found New Hardware” prompt each time you boot.
• Check the system Event Log to confirm that the PCD driver is running

• STATUS: Windows NT (limited use)

• This is only supported as a PrintDrive Satellite (when combined with another PrintDrive
Server on Win2000/2003).
• Create an “PrintDrive Series 2 Restore” input device on the WinNT PC
• Jobs imported are decompressed using PCD, and are converted to software compression.

32 Agfa Graphics: an introduction 30.12.08

Features sometimes overlooked in Update F
 Features sometimes overlooked in Update F

• Text Replacement Variables

• File name overrides

• Customized finishing marks

• CIP3 filename and parameter overrides

• Scripts

• Open Connect filename encoding

34 Agfa Graphics: an introduction 30.12.08

 Text Replacement Variables
• PrintDrive Update F expanded the set of text replacement variables,
and introduced several opportunities where these can be used.
• Text replacement variables may be in cases where data (specific to
the job or the processing) is resolved at run-time for:
• Finishing marks
• Output file names
• Executing Scripts
• CIP3 parameter processing

• Please review the following document:

“TN Apogee PrintDrive S3 Update F Text Replacement Variables”
PDS3_TextReplacementVariables.doc/pdf

• This describes the different variables recognized by PrintDrive (e.g.

$JOB, $COLOR, $WEB, $SIG …), and lists which variables may be
used in specific contexts.

35 Agfa Graphics: an introduction 30.12.08

 Filename Override
• Text replacement variables may
be used to customize the output
filenames used by the following:
• TIFF-Out
• PS Proofer
• PDF Proofer

• CIP3 (see later)

• This may be used to adapt the

output filenames to the
requirements of the customer site,
or other 3rd party software.

• The use of the filename override

is optional. If left blank, the
default file naming convention for
the device will be used

36 Agfa Graphics: an introduction 30.12.08

 Finishing Marks
• Users may create finishing mark files • A common use for finishing marks is to
on PrintDrive to add text and marks to position the exposure wedge so that it
each plate image. Multiple elements does not conflict with the clamps,
may be added anywhere on the plate punches, or plate image.
image. • Here is an example that has been
• Text replacement variables may be used with PrintDrive when outputting
used to customize the text or specify TIFF files to PlateMaker for use on
the TIFF files. the Avalon N
• Elements supported:
• Text (e.g. “Donna’s Printing”, /=========================
POINTSIZE=6
“Job=$JOB $SHEET $COLOR
Plated=$DATE $TIME) PRINTMODE=DEFAULT
• TIFF files (e.g. “Donna’s Logo.tif”,
“optical-mark-$RES”.tif) / Move the current reference position by x;y
/ x < 0 moves left, x > 0 moves right
• rectangles / y < 0 moves down, y > 0 moves up
• Legacy PrintDrive “sluglines” MOVE=0;0
• Other processes may be applied / Use a legacy “ThermoFuse” slug line that
(knock-out, double-burn, overprint) / includes the control string.
/ Position it centered along the right edge
/ with the baseline toward the edge
• Please review the following document: SETREFERENCE=S
“TN Apogee PrintDrive S3 Update F Finishing Marks” ORIENT=0
MOVE=0;6
PDS3_FinishingMarks.doc/pdf
SLUGLINE=(ThermoFuse)
/=========================

37 Agfa Graphics: an introduction 30.12.08

 CIP3 filename and parameter overrides

• The CIP3 files generated

by PrintDrive are generally
compatible with press
vendor software.

• However, there are

instances where
customization is required
to meet the needs of the
press software.
• file name format
• various CIP3 parameters

38 Agfa Graphics: an introduction 30.12.08

 References Available: InkDrive
• Please refer to the following PrintDrive documentation for technical
description of features specific to CIP3:
• PrintDrive Update F Service Pack 4 release notes
• description of file name and parameter overrides
“TN Apogee PrintDrive S3 Update F Service Pack 4”
TN Update F Service Pack 4.doc

• PrintDrive Update E release notes

• how to use RegEdit to change signature ID for CIP3 (e.g. convert all sigs to “Front”;
determine “front/back” via odd/even rule)
“TN Apogee PrintDrive Series3 update E”
PrintDrive _RN_E_3_26_04.pdf

• PrintDrive Series 3 user guide

• How to configure InkDrive device settings for WEB PRESS.
• Size of paper
• Position of image on the paper
• Size of lockdown for lead and trail edge
“UG Apogee PrintDrive Series 3 Administrator”
Administrator.pdf

• TechNote: Describing how to set up PrintDrive and ApogeeX for these use with
GOSS web press systems
“TN GOSS Compliant Web CIP3”
TN_GOSS_Compliant_Web_CIP3.pdf

39 Agfa Graphics: an introduction 30.12.08

 Scripts
• PrintDrive allows customers to
configure an output device to run
a batch file (.bat) or Visual Basic
Script (.vbs) either at the
beginning or end of each image.

• Text replacement variables allow

the user to pass job-specific data
as command line parameters.
• These may be used as progress
or message files with 3rd party
workflow applications.
• A script is provided for use with
Delano

• See PrintDrive Update F release

notes
“TN Apogee PrintDrive S3 Update F”
PDS3_UpdF_ReleaseNotes.doc

40 Agfa Graphics: an introduction 30.12.08

 Open Connect filename encoding
• The PrintDrive Open Connect “Filename Encoding”
workflow was introduced to allow 3rd party vendors to
specify signature information in the TIFF or DCS files
that will be decoded by PrintDrive during import.

• This has been used in conjunction with Prinergy.

• See PrintDrive Update F release notes

“TN Apogee PrintDrive S3 Update F”
PDS3_UpdF_ReleaseNotes.doc

• The filename encoding workflow requires the 3rd party

vendor to generate TIFF or DCS as per a template
(described in the release notes).
• TIFF: jobName^<opt Surface>^<ID>^<color>^<opt web>.tiff
• DCS: jobName^<opt Surface>^<ID>^<opt web>.eps

41 Agfa Graphics: an introduction 30.12.08

Duplex Proofing
 Duplex Proofing

• Engines supported

• Basic requirements for duplex proofing to be

successful

• Automated usage

• How and when to use <variables> to achieve

front/back alignment

• Other alternatives

43 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing : Engines Supported
• Agfa Sherpa
• “AgfaJet GrandSherpaMatic”
• “AgfaJet SherpaMatic 43”
• “AgfaJet Sherpa 2”

• Epson K3 printers – operated in manual load mode

• “Epson X800 (Duplex)”
• “Epson x880 (Duplex)”

• Barco/Gerber printers that use HP base engine –

operated in manual load mode.
• “Impress 2000”
• “Impress 750”

• File-based
• “PostScript Proofer (Duplex)”

44 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing : Basic Requirements
• PrintDrive processing typically involves plate-ready images
delivered from a front-end workflow..
• A press-sheet is positioned somewhere on the plate-ready image.
• HINT: The press sheet is often not “centered” on the plate image.

• There are a few important details that must be satisfied for duplex
proofing to succeed:
A. Ability to center the press sheet:
1. extract the press-sheet from the plate image, OR
2. trim image data from the plate image, whereby the resulting image
includes a centered press-sheet
• WHY? The image sent to the proofer must have the press sheet centered
in order for the front and back images to align.

B. Workstyle (sheetwise, perfecting, work & turn / tumble)

• WHY? Required in order to rotate front/back sides to align properly.

C. Orientation that the plate will be used on press

• WHY? The orientation of the press sheet on press (e.g. wide – sheet
press, or tall – Sunday web press) influences how the front/back will be
rotated to align.

45 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing : Automated Usage
• With Apogee Prepress, ApogeeX, and Apogee Series 3, details are
provided allowing automated output of duplex proofs from
PrintDrive.

A. Center the press sheet:

• AUTOMATED!
• Front-end provides coordinates of the press-sheet on the flat. PrintDrive
can print only the press sheet area, excluding the rest of the plate image.

B. Workstyle (sheetwise, perfecting, work & turn / tumble)

• AUTOMATED!
• Front-end provides the workstyle of the job. PrintDrive uses this to
determine the proper rotation of front/back on the duplex proof.

C. Orientation that the plate will be used on press

• MAY REQUIRE ATTENTION!
• NOTE: PrintDrive does not intelligently determine the on-press orientation
based on input from the front end. In some cases manual intervention is
needed.
• When processing a duplex proof, PrintDrive always assumes that the plate
image is oriented to be mounted on press in the wide dimension.
• If the plate is oriented TALL on press, then the user must encode the
substring <#> in one of various locations. See section following slides.

46 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing: using “<variables>”
• With Open Connect (or early Apogee) workflow insufficient data is
available for automated duplex proofing.
• A series of substrings are available to the user, and may be encoded
in any certain locations. This allows the user to supplement the
parameters needed for duplex proofing, and do so using print
settings.

• CAVEAT: This encoding scheme was originally added with PrintDrive

Series 1, and provided a crude, ugly, but otherwise effective means of
controlling duplex proofing requirements.

• All substrings are contained within brackets: e.g. “<variable>”

• Substrings may be included in any of the following locations. When

the job is processed, PrintDrive will search for these:
• Job name (e.g. “color brochure <tmb>”)
• Proofer device name (e.g. “sherpa <p>”)
• Media name used with proofer (e.g. “36in paper <#>”)

47 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing: using “<X/Y>” to center press sheet

• “auto-trim” substrings may be Component Description

used to “center” a press X value Use when an X-axis punch offset value is
sheet for a duplex proof. used in the imposition. This shifts the press
sheet on the flat parallel to the wide axis. To
• These have no effect on high- compensate for this shift, PrintDrive trims
resolution imaging. twice the punch value from the edge of the
media.
• Auto-trim substrings specify Y value Use when a Y-axis punch offset value is
an amount to remove from used in the imposition. This shifts the press
sheet on the flat parallel to the narrow axis.
the plate image to yield a To compensate for this shift, PrintDrive trims
twice the punch value from the edge of the
centered press sheet. media.
• PrintDrive excludes the auto- Xcut value Trims a specific amount off of the wide axis
of the job. Use to trim excess distance to
trim area on-the-fly during gripper edge that prevents this job from
output to the proofer. printing on the duplex proofer.
Ycut value Trims a specific amount off of the narrow
axis of the job. Use to trim excess distance
to gripper edge that prevents this job from
• For full details, see PrintDrive printing on the duplex proofer.
Series 3 Operator’s Guide, value The value used in the trim. This value may
page 140. be positive or negative.
“UG Apogee PrintDrive Series 3 Operator”
Operator.pdf

48 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing: using “<X/Y>” to center press sheet
<X –0.25> This may be used with a punch offset
of 0.25 inches in the “-“ direction.
• These illustrations To compensate for the punch offset,
depict a rendered “flat” 0.5 inches (2x the punch offset) will
be trimmed from the BOTTOM edge
as the large rectangle of the proof job.
and the “press sheet”
as the gray area
<X 2.54cm> This may be used with a punch offset
therein. It is the “flat” of 2.54cm (1 inch) in the “+” direction.
To compensate for the punch offset,
which is rendered to 5.08 cm (2 inches) (2x the punch
PrintDrive, and which is offset) will be trimmed from the TOP
edge of the proof job.
printed to the output
device.
<Ycut 3.5in> This may be used with a Work &
Tumble job to compensate for
distance to gripper edge that causes
misalignment of duplex proof jobs.
This will trim 3.5 inches from the
LEFT edge of the job.

<X –25.4mm Ycut This may be used to compensate for

-3.5in> a job that:
•uses a punch offset of 24.5mm, and
•has job offset 3.5” in Y-axis which
results in a flat which is too large in
the narrow axis..
This will trim 50.8 mm (2 inches) (2x
the punch offset) from the LEFT edge
of the job, and 3.5 from the BOTTOM
of the job.

49 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing : using “<variables>” for workstyle
Substring WorkStyle (default) value
• This table lists the substrings in registry

that may be encoded to <1> single-sided "1"

specify the workstyle. <p> perfecting "2"
<perfect> perfecting "2"

• Many of these are redundant, <perfecting> perfecting "2"

mostly due to suggestions <pf> perfecting "2"

received over time. <prf> perfecting "2"

<sw> sheet wise "0"
<t> work & tumble "4"
• Example: Jobname <tmb> work & tumble "4"
• “color brochure <tmb>” –
<tumble> work & tumble "4"
process this as a work &
tumble job <wtl> work & tumble "4"
<wtn> work & turn "3"
• Example: Proof device name
• “sherpa <p>” – process all
jobs to this device as •These substrings & workstyle
perfecting settings are saved in the registry.
• Example: Proof media name •If necessary, additional substrings
• “36in paper <wtn>” –
for workstyle may be added in:
[HKEY_LOCAL_MACHINE\SOFTWARE\Agfa\Pri
process all jobs using this ntDrive\AGFAOutputControl2\param\Work
media as work & turn. StyleMap]

50 Agfa Graphics: an introduction 30.12.08

 Duplex Proofing: using “<#>” to specify TALL-on-press

• PROBLEM:
• Flats may be composed to be loaded onto press in a WIDE orientation (where the gripper
edge is on the long axis of the plate), or in a TALL orientation (where the gripper edge is on
the short axis of the plate).
• For duplex proofing, always assumes flats to be printed in a WIDE orientation based on the
width and height of the flat.
• However when TALL flats rendered to PrintDrive, duplex proofs may not align properly
based on the workstyle used.
• Unfortunately there is no information in the job describing how the plate will go on press.

• WORKAROUND:
• Encoding “<#>” into the job name, proof engine name, or proof media name allows
PrintDrive to interpret the flat geometry for a TALL-on-press configuration.
• The substring “<#>” in the job name, proof engine name, or proof media name designates
that the duplex proof should treat the flats as being configured to be loaded on press in the
TALL orientation.

• Example: Jobname = “color brochure <#>”

• Example: Proof device name = “sherpa <#>”
• Example: Proof media name= “36in paper <#>”
• The most flexible option is to encode a proof media name with “<#>”

• For full details, see PrintDrive Series 3 Update D release notes:

“TN Apogee PrintDrive Series 3 v1.0 Update D Release Notes”
SVM_12113315.pdf

51 Agfa Graphics: an introduction 30.12.08

 Duplex proofing : Other alternatives

• There are a few other options that may be used to

permit duplex proofing with non-Agfa workflows.
A. Center the press sheet:
1. Select a sub-area from the thumbnail in the PrintDrive Pilot.
• This can lack accuracy though.
2. If using PrintDrive LE to drive a GrandSherpaMatic, use the
“Adjust Image” option in the TIFF-Input device. This will
automatically pad or clip data from any side of a TIFF file being
imported into PrintDrive LE.
• This is not practical when using the TIFF’s for plating as the image is
changed.

B. Workstyle (sheetwise, perfecting, work & turn / tumble)

1. Use OpenConnect “Import As” to assign the workstyle to any job
being processed through the hot folder.
• This may require a separate hot folder if multiple workstyles are used
by the printer.
C. Orientation that the plate will be used on press
• No other options. You still have to use “<#>”

52 Agfa Graphics: an introduction 30.12.08

What is “Allow Server Synchronization”?
 What life was like before server-synchronization
• Initial limitations with ApogeeX/PrintDrive included:

1. Incomplete “work items” could be created when processing was interrupted, or multiple render TP’s used.
E.g.:
• PrintDrive proofing Sheet 1F with only Cyan and Magenta received.

2. When a job element is deleted from the ApogeeX Client, the job element previously sent to PrintDrive would
not be deleted.
• PrintDrive job did not display fact that ApX job was being modified.

3. ApogeX Client user could not stop a job from plating on PrintDrive, or if job was being edited in ApogeeX the
job elements could not be suspended on PrintDrive.
• A job could be plated and put on press with incorrect content.

4. Users could not fully automate ApogeeX/PrintDrive configuration if it was necessary to keep job on
ApogeeX for reprocessing until it was processed and deleted on PrintDrive.
• This required manual intervention to delete jobs from ApogeeX client.

5. Duplicate or missing separations on the PrintDrive job, but the job looks OK on the ApogeeX side.
• Some separations processed by ApX do not display in the job, or multiple (e.g. two Cyan separations on a plage) result.

6. Missing work items on PrintDrive when ApogeeX processed job.

• No InkDrive or Backup work item displayed on PrintDrive.

7. Users with MIS systems could not track job processing results from PrintDrive.
• Messaging from MIS only available from ApX, but not from PD processing.

54 Agfa Graphics: an introduction 30.12.08

 Allow Server Synchronization

• ApogeeX v3.0 (+)

• PrintDrive UpdateF (+)

• Ability to synchronize the job status

between ApogeeX and PrintDrive.
• This is enabled with the “Allow Server
Synchronization” checkbox in the
PrintDrive_TP configuration.
• commonly referred to as “server-sync”
• Refer to the PrintDrive S3 Update F Service Pack 4
release notes for details.
“TN Apogee PrintDrive S3 Update F Service Pack 4”
TN Update F Service Pack 4.doc

55 Agfa Graphics: an introduction 30.12.08

 Allow Server Synchronization
• When “allow server synchronization” is enabled:

1. Using information from ApogeeX, PrintDrive guarantees that incomplete “work items” will not
occur.

2. Automatic synchronization of job changes from ApogeeX Client.

• When flat or page separations are deleted from the job on ApogeeX, the obsolete separations are
immediately signaled to be deleted on PrintDrive ... avoiding the chance that old separations may be
output prior to replacement separations arriving.
• When signatures in a job are modified on ApogeeX, the obsolete signature components are
immediately signaled to be deleted on PrintDrive.

3. ApogeeX Client users can halt job or job element processing on PrintDrive.
• “STOP PLATING”.
• “REJECT” job elements.

4. When “delete after imaging” is selected in an ApogeeX flow that includes a PrintDrive_TP,
then the job will remain on ApogeeX until it is deleted from PrintDrive.

5. The job processing to PrintDrive ensures that no separations will be deleted automatically,
and no separations will be duplicated.

6. InkDrive and Backup work items will be displayed on PrintDrive when the job is completed
processing from ApogeeX.

7. Event signaling allows ApogeeX server to forward PrintDrive processing results to MIS
through JMF messaging.

56 Agfa Graphics: an introduction 30.12.08

 LIMITATIONS

• “Allow server synchronization” must be enabled if using

Versioning with Apogee Prepress.

• The use of “server synchronization” may be disrupted if

the user manually edits job properties from the PrintDrive
Pilot.
• deleting, copying, or renaming separations, pages, or flats
• applying double burn
• editing imposition details

• When a manual PrintDrive job modification is made,

there is no guarantee of the results when subsequent
interaction is performed with ApogeeX.

57 Agfa Graphics: an introduction 30.12.08

PrintDrive LE
 PrintDrive LE
• PrintDrive LE offers a slimmed-down level of functionality. It is
intended as a low-end workflow option supporting equipment sales
(CTP and proofing).
• PrintDrive LE may be used with non-Agfa workflow configurations as a
simple output manager to drive Agfa high-resolution or proofing
devices.
• PrintDrive LE uses the same PrintDrive software, but exhibits “LE”
capabilities when used with a PrintDrive LE dongle.
• When connected to a PrintDrive LE system, the PrintDrive Pilot toolbar
displays the “LE” identifier, and includes a limited set of buttons.

• A detailed presentation of PrintDrive LE is included in the PrintDrive

Update F presentation. Go to slide # 63.
“PR Apogee Series 3 PrintDrive Update F”
PrintDrive UpdF-051118.pdf
• See also the PrintDrive Update F release notes
“TN Apogee PrintDrive S3 Update F”
PDS3_UpdF_ReleaseNotes.doc

59 Agfa Graphics: an introduction 30.12.08

 PrintDrive LE

• PrintDrive LE is available in two versions:

• PrintDrive LE 4-Up (830mm x 676mm)
• PrintDrive LE 8-Up (1160mm x 940mm)
• NOTE: OpenConnect Option is included in PrintDrive
LE

• Supported options and upgrades:

• WebGrowth Option
• InkDrive Option
• Upgrade from 4Up LE to 8Up LE
• Upgrade from PrintDrive LE to full PrintDrive

60 Agfa Graphics: an introduction 30.12.08

 PrintDrive LE: What is supported?
• Import TIFF or DCS from OpenConnect
• Standard OpenConnect TIFF and DCS import supported.
• OpenConnect “HotTIFF” setup allows output directly out of hot folder. This
provides optimized throughput for direct output.
• OpenConnect “Filename Encoding” option allows users to encode signature
information in filenames. (needed for automated duplex proofing to GSM)
• Use of “Adust Image” options to pad or clip data during import. (needed for
automated compensation to align TIFF images front/back for duplex proofing).

• Output to Agfa High-resolution device or Agfa Proofing device

• NOTE: Only one output device at a time may be activated.
• Standard output processing to Agfa film or plate devices, with plate size limits
enforced as per 4-Up or 8-Up license.
• Standard output to Agfa proofing devices (no size limit).
• Usage of “Finishing Marks” to add variable data to image on-the-fly
• Ability to run scripts (.bat/.vbs) at the end of each separation
• Usage of Double-burn and QuickFix on-the-fly during output (not with Hot TIFF)

• PrintDrive Pilot
• Support for Remote PrintDrive Pilots
• Ability to view and edit job properties in PrintDrive Pilot job list
• Thumbnail view in PrintDrive Pilot (except when HotTIFF is used)
• Usage of “Print Sub-Area” from thumbnail view

61 Agfa Graphics: an introduction 30.12.08

 PrintDrive LE: What is not supported?
• Job import/export:
• No support for Backup/Restore (cannot archive & restore PrintDrive jobs)
• Job Import/Export is not available (cannot transfer jobs between PD Servers)
• Cannot input jobs from either ApogeeX or any type of Agfa Apogee workflow
• PrintDrive Series2 Restore capability is not available (no legacy backups)
• Apis-Input not available (cannot import from legacy 3rd party input)
• Satellites
• No distributed processing with PrintDrive Satellites (Hi-Res, Proofing, I/O)
• No support for High-Resolution Satellite Option
• No support for Proofing Satellite Option
• Output:
• No support for VLF Option
• No support for Digital QuickStrip (DQS) Option
• No support for Plate-Pairing/DualLoad Option
• No support for TIFF File Output Option
• No support for Non Agfa Device Option
• Raster Preview not available

62 Agfa Graphics: an introduction 30.12.08

Diagnostic Tools
 DIAGNOSTIC TOOLS

• AgfaTD.exe (TIFF Dump)

• Device Scanner

• Poker.exe

• TIFF Condenser

64 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : AGFATD.exe

• Allows the user to browse to analyze a TIFF file:

• lists all tags in the TIFF header
• describes the image
• verify that the TIFF image data can be read successfully by the
PrintDrive software (if selected)

• This can be useful to evaluate:

• Image width and image height
• Rows per strip (how many lines of image data are in each strip)?
• What resolution is the TIFF image data?
• What compression algorithm is used?
• Is the image data readable, or corrupt?

• AgfaTD.exe is in the PrintDrive install path

C:\PrintDrive\AgfaTD.exe

65 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : AGFATD.exe

• Double click on
AGFATD.exe.
• Click “Browse” and find
TIFF file.
• Typically, we use the
default dialog settings.
• The information is posted
in a “Debug Window”
behind the main dialog.

66 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : AgfaTD.exe
• This is an example of the • ImageWidth = 61039
AGFATD.exe results after • # of pixels in each scanline
scanning a TIFF file:
• ImageLength = 91181
100 ImageWidth SHORT 1 [61039]
101 ImageLength LONG 1 [91181] • # of scanlines used for the entire
102 BitsPerSample SHORT 1 [1] image
103 Compression SHORT 1 [5] LZW
106 Photometric SHORT 1 [0] WHITE is 0
10e ImageDescription ASCII 5 [Cyan]
• RowsPerStrip = 512
10f Make ASCII 5 [Creo] • full ImageLength is broken up into
110 Model ASCII 12 [Renaissance] multiple strips, each with 512
111 StripOffsets LONG 179 [1231244...] scanlines.
112 Orientation SHORT 1 [1] 0 Normal
115 SamplesPerPixel SHORT 1 [1]
116 RowsPerStrip SHORT 1 [512] • XResolution = 2400
117 StripByteCounts LONG 179 [1231236…] • image resolution, used for output
11a XResolution RATNL 1 [2400]
11b YResolution RATNL 1 [2400]
11c PlanarConfig SHORT 1 [1] Chunky • YResolution = 2400
128 ResolutionUnit SHORT 1 [2] Dots/Inch • must be the same as XResolution
131 Software ASCII 21 [RASTLIB
Version 1.0n] for imagers supported by
132 DateTime ASCII 20 [2001:12:11 PrintDrive.
17:49:29]
649 ???? BYTE 44 [0x38 0x42... ]
7c4 ???? BYTE 18 [0x1 00... ] • Compression = LZW
• actual value “5” is referenced in the
TIFF library.

67 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : AgfaTD.exe (invalid)
• This is an example of the • Notice the following possible
AGFATD.exe results after problems:
scanning a TIFF file that may not • Invalid “RowsPerStrip”
import correctly on PrintDrive. • The “RowsPerStrip” value 65511
is the same as the “ImageLength”.
100 ImageWidth LONG 1 [77952] • This means that the entire image is
101 ImageLength SHORT 1 [65511]
saved in a single image strip.
102 BitsPerSample SHORT 1 [1]
103 Compression SHORT 1 [4] CCITTFAX4 • This may fail during import or
106 Photometric SHORT 1 [0] WHITE is 0 processing if insufficient memory is
111 StripOffsets LONG 1 [8] available to read the image strip.
115 SamplesPerPixel SHORT 1 [1] • PrintDrive requires TIFF files to
116 RowsPerStrip SHORT 1 [65511] have image data saved in multiple
117 StripByteCounts LONG 1 [93882705] strips.
11a XResolution RATNL 1 [3200]
11b YResolution RATNL 1 [3200] • The “RowsPerStrip” should be
11c PlanarConfig SHORT 1 [1] Chunky less than the full “ImageLength”.
128 ResolutionUnit SHORT 1 [2] Dots/Inch

• Unsupported resolution
• The “XResolution” and
“YResolution” are 3200.
• This may generate an input error,
as 3200 is not supported by the
imaging engine.

68 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : AgfaTD.exe (invalid)
• When the “Read Image” button is • This is an example of a TIFF file that
clicked, AGFATD.exe will verify that cannot be read by the PrintDrive
the image data can be read by the software.
PrintDrive software.
• This is commonly due to a corruption
• As the utility evaluates the image data, in the TIFF file.
it posts a ‘.’ character in the “Debug
Window” for each block of data read. Reading image 0
strip buffer size = 10240
• Here is a correct example: ...Error reading image 0, strip 2
.Error reading image 0, strip 3
Reading image 0 ....Error reading image 0, strip 7
strip buffer size = 5469696 ...Error reading image 0, strip 10
.Error reading image 0, strip 11
............................... .Error reading image 0, strip 12
............................
............................ .Error reading image 0, strip 13
............................ .Error reading image 0, strip 14
............................ ..Error reading image 0, strip 16
............................ .....Error reading image 0, strip 22
........ .Error reading image 0, strip 23
image 1 complete .....Error reading image 0, strip 41
..
image 1 complete

69 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : Device Scanner

• The Device Scanner utility scans the system and

provides status about the interface cards (PCI and USB)
and connected devices. When an interface card is found
the utility displays:
• the board number – this is the value that is entered into the
PrintDrive “Settings” dialog
• whether or not a device was connected, the device name if one is
found, and a message if the device connection is currently in use
by another application
• a note indicating whether or not this device requires a STANDARD
or “LV APIS” UPAC board

• See also the PrintDrive Update F release notes :

“Appendix E: Device Scanner”
“TN Apogee PrintDrive S3 Update F”
PDS3_UpdF_ReleaseNotes.doc

70 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : Device Scanner

• Options for using the

Device Scanner utility
• may be run automatically
to scan for when the “Run
‘Scanner’ Utility” button is
clicked in the PrintDrive
Pilot Device Properties
“Settings” page.

…OR…

• Browse to PrintDrive install

path (C:\PrintDrive) and
double-click on
“Device_Scanner.exe”.

71 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tools: Poker.exe
• The Poker.exe utility
was developed to:
• View and edit
parameters in the
PrintDrive database in a
manner that would be
recognized by the
PrintDrive services via
notification.
• Enable debug tracing
for PrintDrive services.

• The most common

usage is to enable
“Device Information”
tracing for output
devices.

72 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tools: Poker.exe

• When output device tracing is enabled, the results are:

• Logged to the PrintDrive Pilot Device Properties “Status” window
• Automatically saved on the PrintDrive Server or Satellite in the
C:\PrintDrive\LOG\ directory when the device is STOPPED.

• This tracing data is fairly verbose and may only yield

recognizable results when examined by engineering.

• WARNING: Keeping the output device tracing enabled

when not needed may slow down performance of the
PrintDrive Pilot.

• See also the Poker.exe tech note:

PDS3 Poker.pdf

73 Agfa Graphics: an introduction 30.12.08

 Diagnostic Tool : TIFF Condenser
• The TIFF Condenser utility is provided to optimize performance
when using large TIFF files to provide plate marking with the
PrintDrive “Finishing Marks”.

• This utility takes a “large” TIFF image and generates:

• a set of small TIFF images, and
• a companion Finishing Mark text file.

• These output files are used as an alternative to the “large” TIFF

image, and provide a faster method of placing all of the marks from
the “large” TIFF image in the correct location.

• This standalone utility is run from the PrintDrive install directory.

• See also the PrintDrive Update F release notes : “Appendix B: Using

the TIFF Condenser Utility”
“TN Apogee PrintDrive S3 Update F”
PDS3_UpdF_ReleaseNotes.doc

74 Agfa Graphics: an introduction 30.12.08

Suggestions for managing Apogee X/Prepress
import of PrintDrive S2 and S3 “backup” jobs
 PrintDrive Backup Jobs

• Description of PrintDrive Series 3 backup jobs

• Description of PrintDrive Series 2 backup jobs

• Using “AGFATD.exe” to check compression of

images in PDS2 backup jobs.
• Watch out for hardware compression!

• Importing PDS2 backup jobs into Apogee

Prepress

76 Agfa Graphics: an introduction 30.12.08

 PrintDrive S3 “backup” jobs

• PrintDrive Series 3 “backup” jobs consist of a

number of files saved in the backup directory
configured on PrintDrive.
• The job file structure is nearly identical to the file
structure of the PrintDrive Raster Data jobs.
• The TIFF files are compressed with Agfa
Software Compression, unless jobs are imported
with Open Connect “keep native compression”.
• There are no instances where a PCD board is
used to create a PrintDrive Series 3 backup job.

77 Agfa Graphics: an introduction 30.12.08

 PrintDrive S2 “backup” jobs

• PrintDrive Series 2 “backup” jobs consisted of

a single TIFF file including multiple images (a
“multi-doc” TIFF).
• For example, a backup job may be named:
• 5320 NNFF #10 Envelope(36961).tif
• Depending on the PrintDrive release used to
create the backup job, the image data could be
compressed using:
• Agfa Software Compression
• Hardware Compression (PCD board)
• The internal compression format of a PrintDrive
Series 2 archive is not visible to the end-user.

78 Agfa Graphics: an introduction 30.12.08

 Using “AGFATD.exe” to check compression
• The “AGFATD.exe” utility may be used to check the
compression format. TIFF header data for multiple
images will be displayed in the “Debug Window”.
• Check the compression of a high-res file, but do not check
thumbnail images. See the “SubFileType” key:
• High-Res = “fe SubFileType LONG 1 [0]”
• Thumbnail = “fe SubFileType LONG 1 [1] Thumbnail”
• See the “Compression” tag:
• If it is “[512] ALDC1”, then it is hardware compressed.
• Example of job using PCD hardware compression:
fe SubFileType LONG 1 [0]
103 Compression SHORT 1 [512] ALDC1

• Example of Agfa software hardware compressed job:

fe SubFileType LONG 1 [0]
103 Compression SHORT 1 [514] ASWC

• NOTE: Example of thumbnail (not relevant!... Always

packbits compressed!):
fe SubFileType LONG 1 [1] Thumbnail
103 Compression SHORT 1 [32773] Packbits

79 Agfa Graphics: an introduction 30.12.08

 Importing PDS2 backup jobs into Apogee Prepress

• Apogee Prepress does not import PrintDrive Series 2 (or

earlier) backup jobs.
• To import PrintDrive Series 2 jobs to Apogee Prepress:
1. Use the PDS3 server to restore PDS2 backup job to the PDS3
job list
2. Back up the job from the PDS3 job list
3. Import the PDS3 backup job into Apogee Prepress.

• As a rule:
• Do not uninstall PrintDrive until all archives have been imported
to Apogee Prepress.
• If done as a trade-in, a soft dongle may be needed for continued
operation.

80 Agfa Graphics: an introduction 30.12.08

What to gather when debugging is needed…
 What to gather when debugging is needed…
• When a problem or unexpected behavior is seen with PrintDrive, providing
the following info with the problem report may hasten the resolution:
1. Installation history
• See “Installation History” in PrintDrive Pilot “Splash” screen

2. PrintDrive “Tuner” settings file – “pdtuner.pds”

• simulate the customer setup; identify problems with settings

3. PrintDrive Pilot Job Log “Max Info” detail level

• Provide for any job related to the problem.

4. Job folder as-is from PrintDrive Raster Data Folder

• Do not provide a “backup”, as this is not complete

5. APIS_trace.txt file (if problem with APIS device)

6. Poker.exe trace (if necessary)

7. Samples of output exhibiting problem (plate or proofing)

8. Detailed description of was precipitated problem, how problem was exhibited,

and results of error recovery (how did you get the system back on-line?)

82 Agfa Graphics: an introduction 30.12.08