Fixing a Cut Path to Look for Crop Marks

gamerxr72

New Member
I use Wasatch Softrip 6.3 with my Graphtec FC7000-160 cutter and have noticed that sometimes, the cut file ignores the fact that there are cut marks and just starts cutting without trying to read them. Im not sure if this happens to anyone else, but this is my solution incase it does.

Find the path file (.path) and open it in a text editor (I like notepad++).

The beginning of a bad cut file looks like this.

Code:
%!PS Consolidated Path File (from printspoolerlib consolidation)
%%
%% PostScript coordinate system - unit is 1/72nd inch, origin is at lower left corner of pixel map

%%PageSize: 3696.13 1516.8
<< /PageSize [3696.13 1516.8] >> setpagedevice

%%%%CUTMARK_000: 35.2 1480.8
%%%%CUTMARK_001: 3677.87 1480.8
%%%%CUTMARK_002: 35.2 36
%%%%CUTMARK_003: 3677.87 36
%%COLOR: DEVICESPECIFIC

%%COLOR: CUTPATH
And the beginning of a good cut file looks like this.

Code:
%!PS Consolidated Path File (from printspoolerlib consolidation)
%%
%% PostScript coordinate system - unit is 1/72nd inch, origin is at lower left corner of pixel map

%%PageSize: 3696.13 1516.8
<< /PageSize [3696.13 1516.8] >> setpagedevice

%%CUTMARKSTYLE: GRAPHTEC1

%%%%CUTMARK_000: 35.2 1480.8
%%%%CUTMARK_001: 3677.87 1480.8
%%%%CUTMARK_002: 35.2 36
%%%%CUTMARK_003: 3677.87 36
%%COLOR: DEVICESPECIFIC

%%COLOR: CUTPATH
In the good cut file which reads the cut marks, the only difference is line 8:

%%CUTMARKSTYLE: GRAPHTEC1

Or if I am using interval cut marks:

%%CUTMARKSTYLE: GRAPHTECINTERVAL1

The bad file is missing that line entirely. Adding it will fix the file.

You might need to close your rip software to do it.
 
Top