I am trying to cut a very detailed, 22 inch diameter relief. Finish pass is with .0625 ballnose.
To output a single g-code file is too long.... I understand how to use vector boundaries to limit area to be cut.
Here lies my problem...
I cannot find a way to prevent Aspire from splitting the path.... It starts in the middle (climb) of the vector limits, cuts outside half, then goes to the inner boundary, and cuts back to center.
This creates fragile ridge in the middle, one that chips as the ridge gets more narrow.
I want to start at inner boundary and spiral (step) to the outer boundary. I could live with the reverse order.
I am having to create a "false" boundary at double the distance, write the code, then spend 30 minutes deleting the second half..... I say 30 minutes but it can be more. The code file can have 300,000 lines of code AFTER deleting excess.
I am starting to think I m not going to be able to use Aspire for large projects. It is not the length of the code file. It is the strategy....
(I am aware of using raster, but this runs X/Y, not circular)