Why is there not an “insert pause” between operations to facilitate tool bit changes? This would eliminate creating and keeping up with multiple g-code files. Seems like it would be a simple program update.
Because in addition to a pause, there needs to be a way to let the user re-zero (since the new tool is not the same length as the previous one). So “just” adding a pause would not work.
What you describe (multiple toolpaths in a single file) is exactly what happens when you have the BitSetter installed and enabled in the machine configuration : Carbide Motion will pause the program, prompt you to change the bit, then proceed to measure the new length using the BitSetter, and continue the job.
Cool. Perfectly addresses the issue. Thanks so much!
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.