Skip to main content
T
TomD.inPDX17-Peridot
17-Peridot
June 3, 2013
Question

Is anyone familiar with Enroute software?

  • June 3, 2013
  • 1 reply
  • 1676 views

I have a job that needs to get done on a CNC router bed. The owner says that the DXF file needs to be all polylines. That is so 1980's!

 

DXF exports have been using lines, arcs, and ellipses since Autocad 13. Why am I being told that Enroute requires polylines? Is it just the owner seeing jaggies on the screen and calling foul? Should the tool offsets recognize the ellipses and properly interpolate them?

 

I really don't want to go through the effort of trying to make polylines out of every form that I need processed.

 

Alternatively, is there a DXF converter that will make polylines out of every entity in the file?


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

1 reply

G
gkrishna1-Visitor
1-Visitor
June 3, 2013

splines and ellipses don't get love from CNC machines http://cadsetterout.com/autocad-tutorials/cad-to-cam-cleaning-up-dwg-files-for-cnc/

T
TomD.inPDX17-PeridotAuthor
17-Peridot
June 3, 2013

Funny thing is, the owner now calls for the individual files as being good but not the full sheet. I think his on-screen graphics are fooling him. I exported 11x17 of each part and he is happy. I exported 48x96 and he isn't. Each segment is exactly the same definition in both dxf files; lines, arcs, circles, ellipses and polylines.

Creo does pretty good with the polyline option for splines. It outputs a very dense polyline. But not for ellipses as they are defined like arcs with a center and size.

I will see what comes of this in the prototype run.

Terms & ConditionsCookie settingsAccessibility statement