ManitobaKeith wrote:One other thing I have heard is that there is no 3D arc output by Aspire or V-carve and Mach3 is not capable of arcs. So, what's the big deal with arcs - I don't know a lot, so please explain.
There is a lot of misconception about arcs. And when I say arcs I mean G2 an G3 commands. Where the controller (Mach3, WinCNC, Fanuc etc.) interpolates an arc movement from a set of gcode command parameters.
Aspire and Vcarve Pro can most certainly output G2 and G3 commands in gcode but only in 2D toolpaths. Not in vee-carving or 3D.
I think what confuses people is that the post processor that they use says "arcs" as part of it's description.
What that means is that post processor will post G2 an G3 moves where appropriate only in a 2D toolpath
If a non arc post processor is used, then even 2D toolpaths will contain no G2 or G3 commands. They will automatically be segmented.
As far as Mach3 is concerned, like all controllers that run gcode, it does not interpolate arcs on a rotary axis. A, B or C.
The issue is not that wrapping has introduced this limitation. It is built into gcode. It is already there. It is industry standard.
Mach3 does use G2 and G3 movements in a flat plane. X-Y, X-Z or Y-Z. As do most other gcode capable controllers.
The important part of all that is, that in rotary axis work that we do with our 4th axis, the gcode that we use will for the most part will contain no arcs.
And for the very rare occasions (I can not think of an example) that 2D toolpaths are used with arcs then segmented code will make no or little difference.
Hope that makes it clearer.