FAQ
Short answers about DERCAR ID Cut, licensing, production workflow and DT setup.
DERCAR ID Cut prepares ID Cut jobs for Mimaki CuttingLink directly from Adobe Illustrator or CorelDRAW: it creates Barcode, marks, the FC cut layer and service files in the CuttingLink DT folder.
The current public release of DERCAR ID Cut is for Windows. macOS is being considered separately, but it is not part of the current public release.
DERCAR targets original Mimaki CuttingLink and its standard DT workflow. CuttingLink is not included with DERCAR: download the current version from the official Mimaki website and check compatibility with your equipment.
For print shops, sign production, Mimaki service teams, dealers and workshops where printing, Barcode and contour cutting are tied to real deadlines, material and waste.
In the standard flow ID Cut is tightly tied to a Mimaki printer/RasterLink. DERCAR moves Barcode and job preparation to the layout stage, so printing can use the shop’s RIP and any suitable printer while cutting remains in original Mimaki CuttingLink.
The main workflow is built around Adobe Illustrator and CorelDRAW. A separate DERCAR ID Cut Operator utility is used on the cutting operator side.
No. DERCAR does not replace CuttingLink and does not repackage it. DERCAR prepares jobs, Barcode and contour data, while cutting is still performed in original Mimaki CuttingLink.
Yes. The main idea of DERCAR is to decouple ID Cut workflow from mandatory Mimaki printing. Printing can use another printer and RIP if the production flow preserves correct marks, Barcode and material for cutting.
DERCAR ID Cut was created inside a print shop by a programmer, designer, printer and cutting plotter operator working together. It comes from real production, not from an abstract lab workflow.
Three parts are needed: the DERCAR panel for Adobe Illustrator or CorelDRAW, original Mimaki CuttingLink for cutting, and, when needed, DERCAR ID Cut Operator on the operator workstation.
Yes. DERCAR prepares data for original CuttingLink, but CuttingLink itself is not included with DERCAR and must be downloaded from the official Mimaki website.
RasterLink is not mandatory for the DERCAR workflow. Printing can use the shop’s usual RIP, while contour cutting remains in CuttingLink.
FineCut is not required for the main DERCAR workflow. The layout and contour are prepared in Illustrator/CorelDRAW, and DERCAR creates data for CuttingLink.
In Illustrator the panel is available as DERCAR ID CUT through the CEP extensions menu. In CorelDRAW a compact panel appears with Designer, Operator, Settings and DERCAR buttons.
The public Windows build targets Adobe Illustrator, CorelDRAW Graphics Suite 2025 v26.x and Mimaki CuttingLink. CorelDRAW also requires Microsoft WebView2 Runtime.
Russian, English, Turkish, Arabic and Japanese are supported for the site and panel. Additional languages are possible after a separate localization check.
Yes. The panel supports light and dark themes so the designer can work in the editor’s familiar visual mode.
Demo includes 100 full DERCAR ID Cut jobs without time or feature limits. It is a way to test the real workflow on production layouts before purchase.
No. Uninstalling and reinstalling is not intended to reset Demo state, generation limit or protective traces of allowed use.
Solo is for one designer workstation. Band is for a group of up to 5 designer workstations with online seat registration and workstation transfer.
NFR means Not For Resale: a license for demos, dealer training, showroom or internal testing. It is not a customer production license.
DERCAR licenses the designer workstation, not only a specific application. Illustrator and CorelDRAW can use one entitlement on one physical computer within the issued license.
Current public prices: Solo — $150 one-time, Band — $500 one-time for up to 5 designer workstations, Orchestra — $1000/year for dealer authorization, Maestro — from $5000 for OEM/white label and custom integration.
After activation, Solo is designed for local work. Band uses online activation and seat registration, but production work after authorization should not depend on constant server access.
A Transfer Key is used to move a Band seat to a new workstation or restore the correct binding. It is a separate mode in license settings.
Standalone Operator is intended for the operator workstation and does not require a designer environment. In the current model it does not require separate activation and is not limited like the designer panel.
Contact DERCAR at dercar@ya.com. For dealer, NFR, Orchestra and Maestro terms, describe your equipment, production scenario and number of workstations.
The designer prepares the layout in Illustrator or CorelDRAW, DERCAR creates Barcode, FC layer, HPGL/DT data and .info, then CuttingLink uses this data for cutting on Mimaki.
Designer creates the technical FC layer from selected contours, sets Barcode/mark stroke parameters and generates the ID job. Marks, Barcode and an ID text block appear in the layout.
Operator is used on the cutting side: it lets the operator select the job ID and manage copy counts by changing CuttingLink data without opening the design application.
ID is a job number linked to Barcode and a file set in the DT folder. The operator sees the ID in a text block on the layout, enters it in Operator and sets the required run.
They are relative axes of a specific job marked by color flags. They do not mean fixed horizontal/vertical. The operator looks at the material and enters copies along the blue and red axes for the current load.
If several designers create jobs into one shared DT, each should have a separate ID range. This prevents two workstations from creating the same number and mixing jobs.
Current compatibility: Mimaki printers CJV330, CJV300 Plus, UCJV330, UCJV300, UCJV150; Mimaki cutters CG-AR and CG-FXII Plus; Mimaki flatbed CF22-1225 and CFL-605RT.
The user. Before production, check the layout, ID, run, material, DT/HPGL data and first cut. DERCAR automates preparation, but it does not replace production control.
DERCAR does not disclose internal HPGL algorithms, encoding, license internals, protected server-side details or ways to bypass/reset Demo or licensing.
The simplest scenario: install the DERCAR panel, install Mimaki CuttingLink and use the standard CuttingLink DT folder on the same computer. No network setup is required.
CuttingLink usually runs on the operator PC. Its DT folder must be available to the designer PC through Windows share or synchronization. In the DERCAR panel the designer points to the shared DT resource.
Use one shared DT resource on the operator PC, file workstation or server. Designer stations write jobs to the shared resource, and CuttingLink reads them from there. Separate ID ranges are important.
An SMB share exposed to the internet is a bad option. For remote designers, synchronize the DT folder instead. The basic recommendation is Syncthing; other sync tools or VPN scenarios such as Tailscale/ZeroTier are also possible.
DT is the CuttingLink working folder where DERCAR writes generated ID jobs. The designer panel, Operator and Mimaki CuttingLink must see the same actual DT data set.
The standard CuttingLink path is treated as the workflow contract. In public DERCAR settings, use the standard CuttingLink DT folder first; non-standard paths are an expert scenario.
A UNC path such as \\ComputerName\CuttingLink_DT is usually more reliable for applications than a mapped drive letter. A letter can be available to the user but invisible to an application running in another context.
Yes, but it must be a separate tested tool. It can help install Syncthing, configure hidden startup, Windows autostart and the standard DT folder, but Syncthing device pairing still requires user participation.
On Windows, the reliable way is Task Scheduler. Start Syncthing with --no-console --no-browser so it does not open a console or browser. Management remains available through http://localhost:8384.
Check that the designer really generated the job, the ID was entered without mistakes, the DT folder is shared or synchronized, Syncthing has no errors, and CuttingLink and DERCAR on the operator side point to the same DT folder.
Check access rights, folder existence, network path, synchronization and whether the path in Designer, Operator and CuttingLink points to the same actual DT resource.