After watching this IDC woodcraft video, I was curious to know if this same information translated into the Carbide Create, Carbide Motion environment.
So I created a test file (attached), in the file I created two circles.
The first circle was created with the circle tool which resulted in 4 nodes…
The other object was a cut and paste of the first circle, which resulted in a lot of nodes.
I then created contour toolpaths to follow those objects, and looked at the generated Gcode.
Both objects resulted in the same ~256 lines of “X” + “Y” Gcode commands.
Check my logic: I drew two conclusions with my limited understanding of Gcode.
(1) For the Carbide Motion + Carbide Create environment, we don’t have to worry about improving performance by decreasing the quantity of nodes.
(2) Does this mean the exact same project in different software would result in faster (smoother) result? Because it would using less Gcode, I’m assuming Gcode that drew curves rather than straight lines? Some quick google searches led me to believe this would be “G2” or “G3” commands, which I’m assuming Carbide Create does not generate?
NodeTest.c2d (68 KB)