After each pass, the code LazyCam generates causes the Z axis to lift before plunging.
Some searching indicated that the lines causing the raising the Z axis could be commented-out, causing the bit to only plunge until it is done with all passes.
Here is that thread:
https://www.machsupport.com/forum/index.php?action=printpage;topic=7577.0So I thought I'd write a tiny command-line application that would modify a .tap file. I'm a competent programmer of command-line utilities.
It would read each line. If the line lifts the Z, the next line would be examined and if it plunges, then the line that lifts the Z would be commented-out.
But in that thread I've linked above, the OP indicated his efforts to comment-out lines didn't work.
So my question is, how does one properly comment-out a line of g-code? I imagine the line #'s have to stay, and the semi-colon is added after the line # and before the commands?
My current project requires drilling a number of holes in four passes, so I think my little command-line utility could save me some machine time and also teach me a little about g-code.
DUMB QUESTION: Maybe there is another way to prevent the ups/downs, and I don't even need to write a small app?