2 tool paths (same bit) in one file

Hey Chris,

what it should do is to enable a comfortable manual tool change at a useful position, e.g. at home position, and provide you with useful popups to achieve the tool change and subsequent Z tool length probing. But the stock script does not to do that, and even worse, it does not lift Z enough to be usable, usually you have not the room to insert a new bit. I don’t know where that faulty code comes from. See also here for two more faulty things in that stock code.

Therefore I provide my working ‘tool-change’ routine here.

There is nothing wrong with this practice. But the more usual situation outside the Onefinity Original Series machines context is that CAM software generates one g-code file for one project, with tool changes (M6 commands) in it. The suggestion to split all g-code file into parts without tool change occurence (CAM softwares offer that option usually) comes from the Onefinity manufacturer who obviously doesn’t want to deal with what’s in the ‘tool-change’ field of the SETTINGS page.

But there are other reasons to split the file into files with only one tool. If you use this practice, you can re-run a pass with one specific tool easily. In this case you would also put the name of the tool into the g-code filename.

1 Like