I have been using Mach 3 with a rotary setup for a while now. I am trying to fix one spot on my code where I am having some build up of weld because the rotary axis stops for a split second. I have several different ideas on how to fix this but I cannot get my code to function like I want it to. Is there a way to turn on a rotary for X amount of time rather than rotating to a degrees. Or is there a way to put a M3 in a line and have the rotary continue to move. I will post my code that I am using below. Between lines N7 and N8 there is a split second stall in the rotary. If there was a way to have that continuously move while the weld tapered out this setup would work perfectly.

N1 (USER 3)
N2 G91
N3 G0 A0.0
N4 M8 (GAS ON)
N5 G04 P1.5
N6 M3 (Start Weld)
N7 G01 A-400.0 F1500.00 (ROTATIONAL SPEED)
N8 A-60.0 M5 (Stop Weld)
N9 G04 P1.5 (DWELL FOR POST FLOW TIME)
N10 G0 A520.0 X-0.400 (MOVE TO NEXT START POSTION)
N11 M30

I've no real idea but my gut feeling is that I would call the F1500 parameter BEFORE N6.
Once executed, the 'F' parameter persists until the next 'F call'.

I've no real idea but my gut feeling is that I would call the F1500 parameter BEFORE N6.
Once executed, the 'F' parameter persists until the next 'F call'.

This does not change anything. The machine has to "think" when it sees the M5 and allows the rotary to stop for a split second. Its like it need to process the code faster.

Quote from: JG on July 16, 2025, 07:52:05 AM

I've no real idea but my gut feeling is that I would call the F1500 parameter BEFORE N6.
Once executed, the 'F' parameter persists until the next 'F call'.

This does not change anything. The machine has to "think" when it sees the M5 and allows the rotary to stop for a split second. Its like it need to process the code faster.

Surely the machine also has to 'think' when it sees the F1500 - and that is within the [Start] [Stop] 'loop' so simply moving that out of the loop ought to have some effect?

Quote from: fpm007 on July 16, 2025, 08:23:21 AM

Quote from: JG on July 16, 2025, 07:52:05 AM

I've no real idea but my gut feeling is that I would call the F1500 parameter BEFORE N6.
Once executed, the 'F' parameter persists until the next 'F call'.

This does not change anything. The machine has to "think" when it sees the M5 and allows the rotary to stop for a split second. Its like it need to process the code faster.

Surely the machine also has to 'think' when it sees the F1500 - and that is within the [Start] [Stop] 'loop' so simply moving that out of the loop ought to have some effect?

I moved it after N5 and it still did not change anything.

At least you tried   

i assume in Config -> Ports&Pins -> Spindle Setup -> General Parameters all Delay timers are
set to zero?

Just an idea.

maybe using M10/M11 might help.

i assume in Config -> Ports&Pins -> Spindle Setup -> General Parameters all Delay timers are
set to zero?

Just an idea.

maybe using M10/M11 might help.

Yes they are.

then M10/M11 might be the way to go, if your motioncontroller support's M10/M11 control?

then M10/M11 might be the way to go, if your motioncontroller support's M10/M11 control?

Briefly looking into this, this might be the way to go. How would I go about setting up M10 and M11 on my controler?