Hi,
I don't know... but in one sense it makes no difference. You have noted that there is a slight pause between
the main Gcode program and macro for instance. I believe that is inevitable as a result of motion control
passing from the main program to the macro. There is no way around that as far as I know.
When a separate chunk of Gcode is required the Gcode interpreter will execute the code by passing P(oint)V(elocity)T(ime)
data to the motion controller, commonly with a buffer of hundreds of milliseconds. Given the buffer who cares
which is fastest, once the buffer is full even a quicker executing piece of code must slow down to the rate
the motion controller consumes PVT data.
Were a chunk of code sooooo.. slow to load say that the motion buffer exhausted BEFORE the interpreter could read and
process the first of the new instruction stream...that would be different.....Mach would pause....and fail. But does
it do that?
Craig