Hey Sean,
in fact, many users of the Onefinity Controller here prefer to choose the option of splitting the program into one program per tool, i.e. creating one G-code program for each tool (the usual CAM programs allow this (which CAM program to use?)).
This is because one of the shortcomings of the Onefinity Controller (and of the Buildbotics Controller, of which it is a hardware and software fork) is that it is not possible to jog around in X, Y and Z during pause or during a tool change (M6 event) (which means the gamepad and the arrow buttons on display are not functional in program mode, not even during pause or tool change). This is one of the big differences to other CNC controllers. It is a requested feature both on the Onefinity Controller and on the Buildbotics controller.
Splitting the overall program into separate parts, one per tool, gets around this limitation in that, as @Bern pointed out, you can then jog around in X, Y and Z at will during tool change, or correct individual settings on the program before starting the pass with the next tool.
With other controllers, this would also work during pause or tool change, without the need to split the program into parts.
Another feature that the Onefinity Controller lacks is the ability to change parameters like the feed rate during the program run. There is however a method to alter spindle speed during pause if you have a Omron or Hitachi VFD (“Temporary ModBus Override”). This also allows to pause spindle during program pause.
You may however go the route of altering the ‘tool-change’ parameters to your needs as I suggested in my previous post, so that you can have multiple tool changes within one program, as is the practice with professional CNCs. The problem with this on the Onefinity Controller is that you can’t always know in advance how long the tools used in your various programs will be. If you enter a high (safe) position of Z at the start of tool change, and then you have to use a tool much shorter than the other tools, the lowering Z routine to probe the tool length in extra slow speed will steal you considerable time. You may judge on if this only happens once during your program, you want to tolerate it, but generally this method is suitable if you have rather similar tool lengths within one program, and adjust them for another program with other tool lengths.