Zund and Kongsberg driver review V6.6

Zund and Kongsberg driver review V6.6

The Zund and Kongsberg drivers have been overhauled in V6.6.0.

All variants of the Zünd and Kongsberg tables have been merged. Each driver now incorporates the various length variations and different output methods .ai, .cut, .zcc, .zip

The driver conversion is done automatically after upgrade.

The Job tracking Feature feeds back to the RIP the copies and jobs cut. It requires the installation of PrintAgent on ZCC or IPC pc. More info can be found here.

    • Related Articles

    • Zund Cut Center RIP Queues

      What? From V6.4.0 onwards it is now possible to make Cut Only RIP Queues for Zund Cut Center (ZCC) drivers. This means that you can submit cut files straight into a hotfolder & the file will be processed and sent directly to the ZCC Job Queue with ...

    • PrintFactory Zund Cut Center integration

      PrintFactory Zund Cut Center(ZCC) drivers have direct bidirectional communication with Zund Cut Center, the software installed on Zund digital front ends. We have made it easy to integrate your Zund cutter into the PrintFactory workflow thus reducing ...

    • Graphtec FC8000 driver settings and workings

      This document explains some functionalities of the Graphtec cutter driver and its workings Settings change for PrintFactory V6 The Graphtec FC8000 driver has been updated with 64 bit dlls in PrintFactory V6.This requires a setting change on the ...

    • Installing an HP Scitex 15000: Driver Selection Guide

      When setting up an HP Scitex 15000, it's crucial to select the correct driver for seamless integration with PrintFactory RIP. Here’s what you need to know: 1. Setting Up PrintAgent The HP Scitex 15000 requires the use of PrintAgent. Before ...

    • IP of Asanti server shows no printers in PF driver info

      Description: Agfa Tauro - JDF/JMF - if the IP entered in the JMF server field in the driver in RIP and it shows no printers, then check the Apache TomCat port used for the setup of the Asanti Server. We auto pick up port 80, but if other port is ...