This-Huckleberry-451

home

Madison Howard

mailnam@mail.com

Profile
Inbox
Activity

Setting
Sing out

?>

timeline
about
photos
friends
more

page you may like

Casino Plus

casino plus login
PHFun casino

Claim Your Bonus
PHFun

PHFun login
Glory Casino

Glory Casino লগইন - Bangladesh

Share Your Mood

This-Huckleberry-451

2024-10-24 18:55:15

PROBLEM: Double-cutting during Kisscutting on the Graphtec Model 8600-160

Recent Notifications

Save as PDF. EPS is a legacy format, PDF does everything else does with less errors.

1729855672
Very good info. You are spot on regarding the path (stroke weight doesn't mean diddly as it is only a visual indicator for the user). No double-cut option used. My files seem totally correct but still had the issues when sending as EPS legacy (which is the format I was told to use during training). However, your suggestion of PDF worked! I wish I had known that I could have been providing PDF files for kisscutting all these years. Being the curious person I am, my Graphtec tech support called me and for 45 minutes we scoured over the EPS files, which they said they suggest and prefer using EPS files. Digging into everything, they said my EPS files looked perfect and couldn't explain why it was double/triple cutting. The current hypothesis they have is that the legacy EPS CS4 file is not being read correctly by the Onyx cut server. They had me email them the file and their team will look it over to try to see if they can find a way for the EPS file to work.

1730196825
Although, I just read that you were using onyx. I love onyx, but sometimes it just drops things while generating the cut file. In the rare occasion that neither EPS or PDF is creating a proper cut file, what I will do is I will save a second file that is just the cut paths. No printing, no nothing, and then I will spool it to onyx as a second job, and the cut path will be fine and I will just use that second dummy job to do the cutting.

1730201699
It's funny you say that. One of my theories is that some of the print information on the non-kisscut layer was interefering with the cut paths. Although that should NOT happen, I had my suspicions about the data on the print layers ... and your suggestion of generating a "cut-only" file would test that theory. Good idea. If it comes down to it, I'll try it. THANKS again!

1730201972