I am using Carbide Create Pro to generate G-Code for an inlay project and am having issues with the Z axis movement at the bit change. All tool paths are created selecting the 1/8th 102 endmill and 60deg 302 V-bit. When the program pauses to switch from the clearing bit to the V-Bit I change out the bits and re-set the Z axis to the top of stock. When the program resumes it moves slightly in the X/Y axis and then immediately and quickly drives the V bit down through the stock.
Looking at the code itself it appears after the T302 command to switch the bits out there is the following command that I am interpreting as a linear drive command to push the bit down in the Z axis by 2.03 inches
G1Z-2.032F304.8
Can anyone confirm that this is indeed the issue or maybe I am misinterpreting the command?
Your program is in millimeters, so that’s -2.032mm
How are you zeroing the 2nd tool? You have manual toolchanges in the program (M0 ;T302)
which don’t use the bitsetter. If you’re not using the bitsetter, you need to output each tool to a separate file. Or you need to use the “Shapeoko” postprocessor to include the bitsetter (Toolchange: M06T302)
Ahhh, okay, that explains why I don’t see a massive negative jump when running in a simulator. Issue has happened twice, both times immediately after the pause for bit change. When the Gsender pauses I change out the bit to the V-Bit and then use a touchplate to set the Z axis, double checked both times that the Z is set to the top of the stock as desired, and then hit resume on the program. This approach has worked for other plugs I have done with no issues at all.
I even went back to the original design, deleted the toolpath and re-generated it as a completely new file and the same thing happened, drives the V-Bit down as hard as it can all the way through the stock
OK, interesting. I have Gsender but I was sure you couldn’t jog or change axis values in the middle of a program. Your pause is the M0 command. I’ll have to go try it now.
Hey Tod, wanted to let you known that as I think you suspected this is likely related either to the Gsender or my specific controller on resume of the program after the bit change Took your advice and split the G-Code in two. When I run the code after the T302 change stand alone no issues at all and a plug was sucessfully made without putting any more undesired holes in my project
Really appreciate your input on this, what a great community we have going here!
