Z axis plunging down while probing for new bit (solved: each tool must be it's own file)

[Aiph5u (Aiph5u (not affiliated with Onefinity))]

Hey Sean,

a g-code file with multiple tool changes works fine with the Buildbotics and the buildbotics-derived Onefinity controller. It’s just that you have to put a useful tool-change routine into the ‘tool-change’ field on the SETTINGS page (there is no useful routine in this field on the stock Onefinity). You can use my Aiph5u’s ‘tool-change’ routine.

But I am not sure if this is your issue. There exist many issues around the Z axis not doing what it should. Search for Z plunge issue. Some are caused by bugs in newer firmware, some by cable breaks in the ‘curly’ Z stepper cable, some are caused by EMI due to the use of non-shielded stepper cables on the machine, and some by bit slipping due to the mediocre ability of the hand trim router’s collet to hold bits (in comparison to ER collets on spindles and 43 mm “Euro” milling motors).

@amsteelle

I am looking specifically for detailed information to help better understand if I do need to save them separately, then why exactly is this the case

Probably the Onefinity manufacturer simply doesn’t want to bother with it. But the original creator of the Buildbotics firmware instructs you how you can enter a useful tool-change routine into the ‘tool-change’ field.

@WaywardWoodworker

@Machinist

@Aiph5u

Many forum members here say the advantages of one g-code program per tool is that you can change the program for a certain tool easier or re-run a pass easier. They put the name of the tool into the file name, and the pass that it is for.

Yes to this. I used to be in the camp where I wanted to keep all tools in the same program. But because I don’t have an ATC and am not running production on anything, I find it more convenient and flexible to actually program for separate tools. So even though I can program for tool changes, I prefer not to.

I was in the “one program per tool” camp until I implemented the tool setter then I found it was easier to and more accurate put them all in one program and use the tool change to measure T1 Z height, switch to tool 2, then measure T2 Z height and automatically reset the Z offset accordingly. This also works well if your Z axis zero point no longer exists after running the first tool path.