Save toolpaths individually or as in one file?

[Ranfy]

I’m a Newby and want advice on saving toolpaths. In VCarve Pro I have the option to save my toolpaths as individual files or all toolpaths in one file. What are the advantages of each option? I have the Onefinity X50 Woodworker. Thanks

[Doconefall]

I save individually to multiple toolpaths instead of as one toolpath.

With the BB controller you can’t recover your position in the program after a crash. You basically have to find your zero again (if you lost it) and rerun the program from the beginning. If you have a very long program you may have hours of aircarving on your hands till you reach your crash point and start carving again. I feel better keeping my carve times shorter in case I need to restart for some reason.

Also if I have a long project I can break it into sessions easier if my toolpaths are separated.

Mike

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

Hey Ranfy,

if you want to use a g-code toolpath file with multiple tools with the buildbotics-derived Onefinity Controller, please be aware that the ‘tool-change’ routine that is delivered with the Onefinity in the SETTINGS page does not work. You can take the ‘tool-change’ routine that I provide here instead.

Further reading

• What will Aiph5u’s tool change routine do?

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

Hey Ranfy,

@Ranfy

In VCarve Pro I have the option to save my toolpaths as individual files or all toolpaths in one file. What are the advantages of each option?

this is a frequently asked (and answered) question. We have a search function in this forum.

@Aiph5u

@Mike01

can you think of any pros/cons of running a single gcode file with multiple manual tool changes vs running them as separate files, one for each tool change?

usually you would say, if your program is well-tested and mature for production, one g-code program with all the tools saves time.

@Aiph5u

@WaywardWoodworker

@Machinist

@Aiph5u

However 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.