Zero location resetting mid-run

[esmiller]

I have been experiencing a wierd behavior.. i was making my first try with Mach3, using an engraving of my wife. The engraving seemed to work properly, but periodically, it would seem to get to the end of the Y run, and, instead of returning to ZERo, it would start the next line beginning where the previos line left off..

any ideas what would cause this?

I eliminated skipped steps, as that would have caused i to atleast return part way to ZERO Y position. Is there a G or M command that i should be looking for in my code that could cause this behavior?

Is it possible for the code to set (or Reset) the current position in Mach 3?

Thanks for any ideas you may have .

Eddie Miller

[ger21]

It won't return to zero unless the code tells it to. Maybe I'm not exacctly sure what you're saying? Are you sure it's not just following the g-code?

[esmiller]

I think it may be following the code, and that there is an error in the code, but it displays perfectly in mach3, and other than it offsetting the Y axis at that point, it appears to run properly.. problem is that point was over an hour into the run, and I am not sure where it reset itself...

My question is whether it is possible that there is an M or G code that is able to reset the currect position..i.e.. I am currectly at Y4, and i want to change that position to Y0. Is this possible in the G-Code?

Eddie

[ger21]

Sure, it's possible.

But, if Mach3's display is correct, and the actual toolpath is not following the display, then you may have lost steps possibly. Does the DRO show the correct location?

[esmiller]

The DRO shows where it THINKS it is .. i.e.. It is now running from Y4 to Y8, instead of Y0 to Y4 .. however, the DRO is still showing Y0 to Y4 .. that is why I was asking if the software could have RESET the DRO position ?

Not sure that makes it any clearer....

Eddie

[ger21]

If the actual position doesn't match the DRO's, I'm pretty sure either your steps/unit is set wrong, or you're losing steps.

Unless maybe you're using work offsets? Is there a G54,G55,G56 or something like that in the code?