stepper wrote: ↑Tue Mar 30, 2021 3:44 pm
The problem we are experiencing is the torch cuts off before the end of every cut,
following extensive troubleshooting I have narrowed the problem down to Mach 3 initiating the M5 command before the end of the cut move
The gcode seems fine. I ran it in my controller and single stepped through every line.
But even just looking at the gcode it's clear the torch should only cut off at the end of the cut path (which includes the leadout).
So exactly how do you know Mach3 is initiating the M5 command. From a troubleshooting perspective that is a little vague.
Do you see your "Torch On" LED on the screen go off before the end of cut for example.
Or does that stay on while the real world output signal to fire the torch goes off. If so how do you know that, via an LED on a breakout board, or via measuring with a multi-meter, etc.
With troubleshooting like this the more specific you can be the easier it is to narrow down the cause.
If you do a "dry run" do you get the same results. A "dry run" is where you turn off THC (so that Mach3 does not require the Arc OK signal to commence motion). You turn off your plasma cutter so nothing is cut. Then run the gcode. You could then even turn down the feedrate heaps so it's much easier to follow what's happening, watch the torch on LED during the cut, etc.
At this point in time, based on what you've told us it seems like Mach3 is having a brain fart. Example a pause should not result in extra material being cut. Where you have entered your pause in the gcode, the cut should complete, the torch should then just stay put (still on) for the delay period, then M5 turns it off. If the torch is still travelling DURING a pause command Mach3 is definitely away with the fairies. Unless of course you have a motion controller card which buffers the step pulse signals, etc, and it's the one having a brain fart, and not doing what Mach3 is telling it to do.
