Catia dxf export9/17/2023 ![]() ![]() Note #4: Our CNC router’s CAM system version can’t accept STEP or IGES. Note #3: The Rhino-exported “toolpath of ten thousand segments” CNC toolpath data runs but the export geometry (a) is simply huge compared to the simple and elegant original data and (b) has way too many random “stop-starts” inevitable with segmented data. ![]() As long as the polycurve is not exploded, everything always blows up the underlying tangent arcs and lines data into segments. Note #2: I have run numerous tests using the “Convert” command with different settings using the CAM Imperial and other export schemes (including the R12 and R14 format factor). We know how to create the necessary geometry. Everything is tangent the data is really clean. Note #1: the original contouring data is “G-Code friendly” arc and straight line-only data. Rhino3D_Perspective_View-PS02F-Forearm_Relief.PNG 1063×485 74.5 KBįrom the numerous Rhino Forum threads (specifically #22469 and #86445),, for CNC/CAM, laser/waterjet data prep, it appears that the only way to “save” the original arc & line data is to explode any/all polycurves prior to export which, unfortunately, defeats the whole purpose of tying the contours together into one long polycurve within Rhino and exporting. ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |