I just used @Tod1d option to replace 92k plus lines in about 2 seconds in a 1770000 line nc file.
My script would have run for about 1770 minutes. NOT !
I changed the replace value from Z0.0 to Z-0.010 for the etching process. That’s what CC uses for the McEtcher.
The TopoMiller output was 0.200 deep that represented 196 meters. So 0.001 is about 1 meter of elevation. This ramp path was set to 0.010 stepdown ( no flat area detection to force a consistent step down ) using a 1/8 ball nose. It will cut in a 16.25 x 11.25 area that matches the original Scallop carve.
I did not think the Ramp would produce the same result if I flattened the original mesh data.
This process is reducing the depth of cut across the whole file.
I guess it’s the same as you are asking ? Yes/No ?
Presumably this program has a Max Depth/Height — if you bracket the cut depth so that Max Depth is 0.014", and Max Height is 0.010" is there a control for what the Depth per Pass is? If set to 0.015", then wouldn’t a single pass be made, with only minimal depth variation? (a range of 0.010–0.014").
I think we are talking the same thing in different words.
The Ramp operation on the original mesh generates the path and needs the height to walk down the model to generate the contours.
The hack of the resulting NC file takes all the cutting Z values to 0 ( I actually am going to -0.010 ) making it suitable for the McEtcher . I use the spring to increase the effective cut in the Acrylic.
As you note, staying under the 0.015 depth it cuts in one pass.
I had to change the S speed to 1 so the McEtcher doesn’t spin ( I do shut off the Spindle controller using the hot button on top). I did change the F feed and T tool number to 503E again to match the CC outputs.
I am going to remake the Ramp path without Lead in/out and Ramp helix
EDIT 2:
Removing the Lead In/Out and changing the Ramp to a Plunge instead of a Helix.
CM had no errors. Sending it.
EDIT 3: I was watching it run an saw a long straight line cut. Stopped the progam.
I realized I had minimum Retract set, so Rapids were under the 0 Value.
I changed the Retract option to Full retract. Looked good, runs good.
The original file had no arcs. Where did they come from? Can you post the new (unhacked) file?
If ramps are only lead in/out, they are not needed for the etcher. Change arc to G0 and use the arc endpoints /modal data as the X/Y coordinates for the G0. Use Z-0.10 or retract height for the Z. If you must go this route, you will need to first code logic looking for arcs and ramp direction so the change only applies to arcs.
I see you are on your way to a remedy. Ignore my gibberish. Cheers.
Watching the etch, the path has a lot of extra points. I made another path after applying smoothing that reduced the .nc file by 2 MB. I will try that one next.
