HIYA IAN, Does that cause a one sec delay in motion?? IF you wait up to 1 sec before motion after the arc starts you may have created a big divot in thin guage metal.
We have the SAME type problem with the slowdown routine for arcs and circle. There is a small delay in motion while the macro runs and makes the cut UGLY.
With Guage metal thinner than 14 we run with NO intentional pause after the arc fires.
THe reason for the 2 step approach with if is IF it sees the signal first test it exits without running the rest of the code. Least time delay. BUT I can see where it may MISS the signal on some systems by asking too soon.
Plasma CAN be a tricky critter.
ALSO some of the THC's plugin WILL "override" anything you try to do. The plugin I run automatically will HALT the system on arc loss or no arc on start.
Thanks (;-)TP
BUT I LIKE the code
DUH, I see where it will start as soon as it sees the signal(;-). The plasma side has lots problems with pauses and delays. I still see MACH3 ignore m3s from time to time AND has delays of motion after the m3 starts. COuld be MACH could be plugins?

? COuld be multiMUXed hardware

?
(;-) TP