To all users of Lasercut 5

[techasist]

I have been using Lasercut 5.3 on my Exlas 1280 since last year with good results. I mostly import Adobe Illustrator files for cutting and engraving.

My issue with this software is that it takes a long time to compile the drawing before it gets transferred to the machine. It happens on very complicated engravings and sometimes the compiling is so bad that there is actually no output at all. I also noticed that the software only uses the RAM of the PC and not the processing power.

Does anyone have these issues?

My PC is connected to the MPC6515 controller on the machine.

Thanks.

[SkipW]

I have LC 5.0 and I have noticed that complex designs do sometimes take a long time to compile.

What seems to help is selecting the whole design first, then under the Tools menu select Unite Lines, with a Unite Tolerance of 0.001

I do that now with every ai file I import.

See what you think.

Skip

[techasist]

Thanks for the input Skip.
I also always do this step and also do Smooth Curve.

On another note, do you know a quick way (automatic setting?) to remove overlapping data after doing the Data Check.

[SkipW]

What program are you using to create the ai files? I've had problems in the past with multiple layers of lines after importing into LaserCut. There could be several copies of the design one on top of the other, but all you see is one. That could be the problem with the files that won't compile at all.

If you use CorelDraw, you can use the Object Manager to make sure the design you are saving as an ai file only has one layer of lines.

And are the line overlaps being created when you import into LC? If so, you have a node somewhere that isn't closed, or you need to add a node as a place holder to keep the line from moving.

I don't think there is a quick way to remove overlaps in LC. But if your file is just one layer of lines, and all the nodes are joined before importing, you shouldn't get any movement of the lines when importing into LC.

I use CorelDraw and always combine the design, then check for and close any open nodes. That has eliminated 99% of the problems I used to have.

Hope that helps
Skip