Thanks Brian:
On a similar note:
I tend to comment my code quite a bit. I put M0's in the code to stop so I can reset the X and Y manually before continuing (don't ask)
I notice that the code and the view screen stop at inappropriate places.
Try the code attached. You will see the following:
1. The code and the display stops at the first M0 as expected. The prompt is in the lower text display. If you do what it says and Zero the X anY axis' you will note that doing so makes the code screen advance one line (to the second M0) as if you pushed the start button again. It then takes two presses of the start button to go forward again.
2. When the code starts again it advances and stops at the G1 BEFORE the next M0 instead of at the M0.
3. On the next press of the start button it stops at the M0 properly.
I'm sure you'll find the problem in my code - I'm still pretty green at it.
It's somewhere in there that the code issued the scream of X axis steps mentioned in my previous post.
You will note there is a tool offset in there. So as you mention maybe it's messing it up. Also I'm sure the double M0 is not too cool. Maybe I'm messing up the look ahead buffer.
Sometimes you need rookies like me to throw odd stuff at your code to reveal the traps.
Thanks
Sage