I have searched and tried everything I can to fix this problem, but I can't find a solution.  Here is my program.  Yes, I can write this all as one movement without a problem, but I will be inserting macros to turn on and off a laser, so I want to test movement first.  I am running in metric, I have all CV controls turned off, I have tried turning on one at a time and changing values without any luck.  I continually get a slight delay between each line of code which causes major problems with our laser application.  Any help is appreciated.

%
g90 g64
g01 a-25. z0. f850.
g01 a-50. z.1 f850.
g01 a-75. z.15 f850.
g01 a-100. z.2 f850.
m30
%

I just posed about the same problem a few minutes ago! I think it is a CV problem, but I can't figure it out either.

Is there a dwell time setting in Mach for the relay?

If you are using the spindle control as a means to activate your laser, there is a delay setting. Spindle options in ports and pins. I dont have a laser, just a wild guess.

I am not trying to activate spindle at all, in fact it isn't even active.  Btw, I am using a Geck0 g540.  To activate the laser I wrote a macro, but I am trying to get smooth rotational movement before I worry about turning the laser on and off at given points.

Do you have a too slow acceleration setting?
John Champlain

I've varied the acceleration to the maximum I can get, on down.  I can't have jerks in the table that the a-axis is controlling at all, let alone between lines of code.

The the toolpath config WHAT do you have set for rotations ?

(;-) TP

I have it set as 360 degrees per rotation.

general config/toolpath/rotations settings ??

(;-) TP