Need some help? Check out our new Help Centre

Cut2D: Extensive cut file for simple plan

I find may interesting free plans at But when I import plan from into Cut2D and convert it to toolpath (1500mm/min on 100%) it generates very long list of instructions - 47.500 lines! Cutting begins quite fast (expected for 1500mm/min) but after 3 objects it significantly slow down and burns moosgumi basis. Checking original plan in Inkscapet it shows objects in plan with < 120 nodes.
Is there any simplifying or simulation option?


  • edited August 2015
    I downloaded that file and looked at it in Illustrator. What I see, like in every dxf file I've encountered, are curves that aren't smooth. They're made up of many short straight lines joined by nodes rather than nice smooth curves that could be drawn with far fewer nodes. I counted ninety nodes on just one small piece of that plan. The piece could have been drawn smoothly with less than half of those nodes.

    As far as I know there's no simple way to reduce the number of nodes on the dxf file other than doing the job manually by deleting unneeded nodes and adjusting the bezier handles to produce true smooth curves. That particular project/plan could be redrawn with less than half the nodes faster than trying to manually adjust the original but that's assuming a proficiency creating and manipulating bezier nodes and handles in a program like Illustrator or Inkscape.

    It doesn't seem right that the machine would slow down as the job progresses. I don't know what would cause that.
  • Obviously problem comes from DXF format in combination with Cut2D.
    If I try to open DXF in Inkscape in save it as EPS, then import eps into cut2d > results in cut file with only 1400 lines of gcode (from dxf 47.500 lines!).

    Another interesting thing are numerous lines of gcode for "dxf variant" - fragment for cutting 3 connected lines:
    N7380 G1 X63.404 Y82.587
    N7390 G1 Y82.580
    N7400 G1 Y82.565
    ...100 lines with G1 Y*
    N8420 G1 Y50.261
    N8430 G1 Y50.256
    N8450 G1 X63.426
    N8460 G1 X63.447
    ...20 lines with G1 X*
    N8680 G1 X65.476
    N8690 G1 X65.478
    N8700 G1 X65.478 Y50.257
    N8710 G1 Y50.262
    N8720 G1 Y50.275
    ... 100 lines with G1 Y*
    N9760 G1 Y82.581
    N9770 G1 Y82.588
    (240 lines of gcode, totaly 3347 for an object with 135 nodes)

    Shouldn't be easier and faster:
    G1 X63.404 Y82.587
    G1 Y50.256
    G1 X63.412
    G1 X65.478 Y50.257
    G1 Y82.588
    (6 lines of gcode, totaly 116 lines for the same object imported from .eps)

    Could be done some optimization in Cut2d?
  • edited August 2015
    The dxf format may work for some people and applications but certainly not for me. As you've discovered it makes for unnecessarily large cut/engrave files.

    So far with the projects I'm using the emblaser for I haven't needed to learn about, or use, gcode manually but I gather it's simple enough to learn and might give more options for using the machine. One of these days I'll devote some time to that.

    Cut2D does have tools for vector/bezier creation and manipulation and maybe other ways to optimize a file but I'm more familiar with the tools in Illustrator so I'll stick to using that program.
  • Thank you for your time. I learned something new and and found solution.
Sign In or Register to comment.