Hi,
I find that whenever I use M3, M5, S0, or S100 that The controller (Mill mode) pauses indefinitely or until I press the Cycle Start button again.
I found this when I tried to stop the spindle motor after moving to Z0.5000 and before moving to X0.0000 Y0.0000. I did this to use the going home time to replace the spindle spin-down delay. As a result, the program never starts or finishes without manual intervention. I tried a variety of G-Code combinations, none of which seem to get past the permanent pause. I have the spindle delays set to 1 sec (spin-up) and 0.1sec (spin-down).  This code snipet was my latest attempt:

N  6  G0 Z0.5000
N  7  G0 X0.0000  Y0.0000 M03 S100
N  8  G83 X0.7000 Y1.0000 Z-0.035 R0.01 Q0.025 F15 G99
...
N 49  (End of Program)
N 50  G40 (Cancel Compensation)
N 51  G43 (Cancel Tool Offset)
N 52  G80 (Cancel Canned Cycles) 
N 53  G00 Z0.5000 (UP)
N 54  G00 X0.0000 Y0.0000 M05 S0 (Go Home)
N 55  M30 (Rewind & Stop Spindle)

Any Ideas?

Bill

In general config, you have options to ignore the tool change, stop and wait, or auto. Might want to play with those a bit.

Brett

What Mach version  and what controller are you using.??
(;-) TP

How does the computer know when the spindle is up to speed or has stopped - is it waiting for these events before it progresses.

I would leave out the speed instruction and see if it responds any differently

Bill I am not quiet sure what you are asking(;-)

The M3,m4,m5 macros are to start forward/rev and stop the spindle.
 The S command is to set the spindle speed.
If you start the spindle with a M3 s100 it will start forward and spool up to 100 rpm. To stop it command a m5 it will coast to a stop.

If you need a delay to allow it to spool up or spin down you have several options.  Configure the delay in Mach or just do a dwell or plan your program movement to compensate for what you need.

Hope that helps (;-) TP

I had this problem  on a PC with Mach installed without the driver. It started around either version 2.20 or 2.40, don't remember now. It paused on all M3's and M5's, and no buttons with VB script would work. Reverting back to an older version would fix it, but none of the newer versions would work. Installing the driver fixed the problem, but it would not work if installed without the driver.