I am extremely frustrated! I am running a job that I have done several times before. I upgraded the computer and replaced the Xylotex controller since running this code. I tuned the motors by measurement and it is off by a couple of thou but that is as close as I can measure.

This is what is happening:





It has happened on another job over an hour into the run. It seems to happen 7/8 ths of the way through the run. THis run has 842 lines of code but the other one has 4500. I thought it might be a memory problem but this run is small.

I am running XP Service pak 2

Do the DROs  and Toolpath show the position of the code or the tool when it goes wrong?
Hood

Is your xylotex getting hot? Looks like one axis may be stopping?

I put the Xylotex in a separate case with a large fan blowing directly on to it.

I didn't pay attention to the exact line where it crashed but when I send it back to 0,0 it is several inches off

Neil

Definitely sounds like an axis stalling then so as Ger says its either the drive or maybe the axis binding in some way.

Hood

If it has been up and down the table over 20 times in this run, is it likely that it would be a stalling axis?

I should really optimize the code but I just wanted to run the same job again.

Neil

I just realized it has occured when doing a circular cut out or pocket.

The circles are never perfectly round.

Neil

IF you will notice there was a total SHIFT in the offset as when it shifted it shifted on the Center point of an arc/circle. AND stayed on the exact center of that arc/circle.  AND still cut a good arc/circle I have seen it shift IN and I have seen it shift OUT.

 THAT is not lost steps or NOISE as if it was the arc would have been offset by the amount of the missing steps AND it would have still cut the same radius as the code here it did none of the above.

And did your DROs show that Terry?
Hood

They certainly did(;-) it was following MACH direction in the dros.

BUT 'll keep quite and let yall handle that, sorry