GregValiant 1,408
The 3D toolpath is a bunch of lines in space. It will contain Travel Moves and maybe Wipe moves and Z-Hop moves, if it is a dual extruder situation then Cura may have adjusted the X and/or Y coordinates to include the extruder offset numbers.
Then there is the offset due to Line Width. Consider a calibration cube 20 x 20 x 20 sliced with a 0.4 line width. The outside wall paths in the X and Y would measure 19.6 x 19. 6 (1/2 line width short all the way around) so it wouldn't be correct to try to make a model from that. (I've done that when all I had was a gcode and I had to design that part to fit with another part. It's no fun.)
I wrote a macro for AutoCad that will read a gcode file and render it in Model Space. The result looks like the model, but it isn't a model. Yesterday I started to alter it so it would read an Arc Welded gcode that was for a Dual Extruder printer. It's not going well (it works but it was processing 600 lines/sec and now it's down to 60lines/sec.).
If you have the STL file then there are conversion utilities (like THIS ONE...you need to create a free account) to turn it into a DXF file that most CAD software can open. The resultant structure (which is not a model) will be comprised of triangle shaped objects rather than parametric bodies or 3d solids. It can be rendered into a colored body and it is the same size as the STL (rather than having nozzle width offsets).
So yes, it might be convenient but I really don't see it happening.
- 1
Recommended Posts
greens83 5
Or perhaps there's a way to export the 3d tool path when it is extruding? This could easily be swept into a 3d model.
Link to post
Share on other sites